Migrating Satellite worker nodes to RHCOS

Step 1: Upgrade your cluster master

Run the following command to update the master.

ibmcloud ks cluster master update --cluster <clusterNameOrID> --version 4.18_openshift

Step 2: Creating a new RHCOS worker pool

• Make sure to specify RHCOS as the --operating-system of the new pool.
• Make sure that the number of nodes specified with the --size-per-zone option matches the number of workers per zone for the RHEL worker pool. To list a worker pool's zones and the number of workers per zone, run ibmcloud oc worker-pool get --worker-pool WORKER_POOL --cluster CLUSTER.
• Make sure to include the --entitlement ocp_entitled option if you have a Cloud Pak entitlement.

1. Run the ibmcloud oc worker-pool create command to create a new worker pool.

   Example command to create a RHCOS worker pool. Note that for Satellite clusters, you must first attach hosts to your location before you can create a worker pool.

   ibmcloud oc worker-pool create satellite --cluster CLUSTER --host-label "os=RHCOS" --name NAME --size-per-zone SIZE --operating-system RHCOS --zone ZONE [--label LABEL]
   

2. Verify that the worker pool is created and note the worker pool ID.

   ibmcloud oc worker-pool ls --cluster <cluster_name_or_ID>
   

   Example output

   Name            ID                              Flavor                 OS              Workers 
   my_workerpool   aaaaa1a11a1aa1aaaaa111aa11      b3c.4x16.encrypted     REDHAT_8_64    0 
   

3. Add one or more zones to your worker pool. When you add a zone, the number of worker nodes you specified with the --size-per-zone option are added to the zone. These worker nodes run the RHCOS operating system. It's recommended that the zones you add to the RHCOS worker pool match the zones added to the RHEL worker pool that you are replacing. To view the zones attached to a worker pool, run ibmcloud oc worker-pool zones --worker-pool WORKER_POOL --cluster CLUSTER. If you add zones that do not match those of RHEL worker pool, make sure that your workloads will not be impacted by moving them to a new zone. Note that File or Block storage are not supported across zones.

Step 3: Add worker nodes to your RHCOS worker pool

See Adding a zone to a worker pool in a VPC cluster.

Step 4: Migrate your workloads

If you have software-defined storage (SDS) solutions like OpenShift Data Foundation or Portworx, update your storage configurations to include the new worker nodes and verify your workloads before removing your RHEL worker nodes.

For more information about rescheduling workloads, see Safely Drain a Node in the Kubernetes docs or Understanding how to evacuate pods on nodes in the Red Hat OpenShift docs.

• Migrate per pod by cordoning node and deleting individual pods.

  oc adm cordon no/<nodeName>
  oc delete po -n <namespace> <podName>
  

• Migrate per Node by draining nodes. For more information, see Safely drain a node.

• Migrate per worker pool by deleting your entire RHEL worker pool.

  ibmcloud ks worker-pool rm --cluster <clusterNameOrID> --worker-pool <workerPoolNameOrID>
  

Step 5: Remove the RHEL worker nodes

Remove the worker pool that contains the RHEL workers.

Consider scaling down your RHEL worker pool and keeping it for several days before you remove it. This way, you can easily scale the worker pool back up if your workload experiences disruptions during the migration process. When you have determined that your workload is stable and functions normally, you can safely remove the RHEL worker pool.

1. List your worker pools and note the name of the worker pool you want to remove.

   ibmcloud oc worker-pool ls --cluster CLUSTER
   

2. Run the command to remove the worker pool.

   ibmcloud oc worker-pool rm --worker-pool WORKER_POOL --cluster CLUSTER