Learn how to successfully migrate workload clusters to a different Linux flavor in a self-managed cloud environment (v.5.9+). Follow our step-by-step guide to onboard, verify, and detach nodes while e
How to Migrate Workload Clusters to a Different Linux Flavor.
Self Managed Cloud Platform - v.5.9 and Higher
All the steps mentioned below are to be done on a single node and not in parallel across the cluster. It is critical that the nodes be migrated one at a time to avoid any impact to the cluster in whole.
Onboard the new nodes to the Management plane with the desired flavor following doc Host management
Verify the host health status as mentioned in the doc Host health status.
Attach the newly added nodes [with new flavor] to cluster. Refer Attach node to cluster.
Verify the Cluster health status from the UI and from the backend using command # kubectl get nodes
Detach the old nodes [with old flavor] from the cluster - Detach node from cluster. Ensure the Active master node [having old flavor] is detached at last.
Again verify the Cluster health status as mentioned Point #4.
De-authorize the node from the Management Plane. Refer doc: De-authorise node.
Remove the old nodes from the airctl config file and configure the hosts again with the required new flavor nodes. Refer doc: Host management
Info
The mentioned steps are applicable only for Multi-master clusters with VIP attached and NOT applicable for Single-master clusters,
Ensure that the cluster is healthy while adding the new flavor nodes.
OS Support Matrix: Support matrix
Last updated
