Cluster Creation Using the Airctl

1. Take a backup of the 5.6 management plane by following the backup guide.
2. Destroy the older1.21 based nodelet cluster using the following commands.

Bash

airctl stop
airctl unconfigure-du --force 
airctl advanced-ddu delete-mgmt

1. Ensure the older/etc/nodelet/airctl-mgmt/certs directory is cleaned up.
2. Download newer 5.9 based artifacts using the download script. Run the install.sh script to extract and place the artifacts under /opt/pf9/airctl directory.

Bash

bash install.sh v-5.9.0-2847602

1. Ensure that the management cluster host has configuration of at least 8vCPU, 32GB memory and 250GB disk.
2. Install the pre-requisite container-selinux package if not installed.
3. Update the config files as suggested below and deploy the new1.25 based nodelet management cluster by running the following command.

Bash

airctl advanced-ddu create-mgmt

Ensure that the airctl-config.yaml file is updated to have the new airctl build number.

In the nodelet-bootstrap.yaml file ensure that systemImages param is set to use newer LTS3 kubedu and nodelet image tar files. And the userImages section points to previous version of kubedu image tars.

Also add isAirgapped: true in nodelet-bootstrap.yaml if it is offline mode. A snippet of the nodelet-bootstrap.yaml is shown below.

YAML

isAirgapped: true
systemImages:
- /opt/pf9/airctl/imgs/kubedu-imgs-v-5.9.0-2847602.tar.gz
- /opt/pf9/airctl/imgs/nodelet-imgs-v-5.9.0-2847602.tar.gz
userImages:
- /home/centos/patch2/kubedu-imgs-v-5.6.7-2624593.tar.gz
- /home/centos/patch4/kubedu-imgs-v-5.6.7-2658688.tar.gz

1. Run the restore command by following the restore guide for 5.6 management plane on top of 1.25 nodelet cluster.
2. Ensure that the DU is in ready state by running the following command and waiting for it to be ready.

Bash

airctl status

After restore, we should be able to login to UI and view the existing workload clusters.

Consul Issue:

After restore, errors seen in the consul pod saying 'ACL not found', which are harmless and can be ignored.

So, we are currently skipping the consul upgrade in the upgrade step and installing the upgraded consul in the restore process itself.