Tag Archives: Migrate

Red Hat OpenShift - Cilium CNI Migration - Header

How to migrate from Red Hat OpenShiftSDN/OVN-Kubernetes to Cilium

Kubernetes, , , , , , ,

Recently, I’m seeing more and more queries about migrating to Cilium within an existing Red Hat OpenShift cluster, due to Cilium’s advanced networking capabilities, robust security features, and enhanced observability out-of-the-box. This increase of interest is also boosted by the fact that Cilium became the first Kubernetes CNI to graduate in the CNCF Landscape.

In this blog post, we’ll cover the step-by-step process of migrating from the traditional OpenShiftSDN (default CNI pre-4.12) or OVN-Kubernetes (default CNI from 4.12) to Cilium, exploring the advantages and considerations along the way.

If you need to understand more about the default CNI options in Red Hat OpenShift first, then I highly recommend this blog post, as pre-reading before going through this walkthrough.

Cilium Overview

For those of you who have not heard of Cilium, or maybe just the name and know there’s a buzz about it. In short Cilium, is a cloud native networking solution to provide security, networking and observability at a software level.

The reason why the buzz is so huge is due to being implemented using eBPF, a new way of interacting and programming with the kernel layer of the OS. This implementation opens a whole new world of options.

I’ll leave you with these two short videos from Thomas Graf, co-founder of Isovalent, the creators of Cilium.

Does Red Hat support this migration?

Cilium has achieved the Red Hat OpenShift Container Network Interface (CNI) certification by completing the operator certification and passing end-to-end testing. Red Hat will support Cilium installed and running in a Red Hat OpenShift cluster, and collaborate as needed with the ecosystem partner to troubleshoot any issues, as per their third-party software support statements. This would be a great reason to look at Isovalent Enterprise for Cilium, rather than using Cilium OSS, to get support from both vendors.

However, when it comes to performing a CNI migration for an active existing OpenShift cluster, Red Hat provides no guidance, unless it’s migrating from OpenShiftSDN to OVN-Kubernetes.

This means CNI migration to a third party CNI in an existing running Red Hat OpenShift Cluster is a grey area.

I’d recommend speaking to your Red Hat account team before performing any migration like this in your production environments. I have known large customers to take on this work/burden/supportability themselves and be successful.

Follow along with this video!

If you prefer watching a video or seeing things live and following along, like I do at times, then I’ve got you covered with the below video that covers the content from this blog post.

Pre-requisites and OpenShift Cluster configuration
As per the above, understand this process in detail, and if you follow it, you do so at your own risk.

For this walkthrough, I’ve deployed a OpenShift 4.13 cluster with OVN-Kubernetes, with a sample application (see below). You can see these posts I’ve written for deployments of OpenShift, or follow the official documentation.

Here is a copy of my install-config.yaml file. It was generated using the openShift-install create install-config wizard. Then I ran the openshift-install create cluster command. Continue reading How to migrate from Red Hat OpenShiftSDN/OVN-Kubernetes to Cilium →

SynologyLogo

Synology – Moving a package between volumes

Storage, General, , ,

I have a Synology 8-bay NAS used for home-lab purposes, but also doubles as local home storage as well.

As part of upgrades, I was decommissioning a volume for a new one with higher capacity drives, however I had Plex installed on the volume to be decommissioned. I moved all the data using the internal file manager, but the package installation remained in place.

Migrate package to another volume

  1. Stop your application via the Synology package center UI.
  2. Login to Synology using SSH and elevate to root.
  3. Use “ls” against /VolumeX/@appstore to find your package folder name
  4. Use “mv” to move the data between the old and new volume, you may need to create the @appstore folder first.
  5. Remove the symlink from the current volume and create the new symlink to the new volume.
  6. Stop and start your package in the Synology Package Centre.

Below is an example the commands I used;

sudo mkdir /volume2/@appstore
sudo mv "/volume1/@appstore/Plex Media Server" "/volume2/@appstore"
sudo rm "/var/packages/Plex Media Server/target"
sudo ln -s "/volume2/@appstore/Plex Media Server" "/var/packages/Plex Media Server/target"

synology migrate package to new volume veducate.co .uk

Now when you try to remove the volume, your package will now show as attached to the volume.

synology remove volume1synology remove volume2

Regards

Dean

Dean Lewis

Profwiz: Migrating users profiles to a new domain

Windows, ,

So a colleague of mine introduced me to this great tool, ForensiT User Profile Wizard.

We were migrating a customer from one domain to a new one, and there is a lot of data stored in the local profile of the users. So we needed a way to move this data into the new profile they will receive when the machine is moved into the new domain.

Note: This is about local machine profiles, and not those on a file server.

1. Login with existing domain\username on the machine, run the Profwiz.exe

  • Enter the new domain name
  • Enter the account name of the user on the name domain

profwiz-1

Continue reading Profwiz: Migrating users profiles to a new domain →