Rollback Guide: From SMCP 5.11 to SMCP 5.10

Prerequisites

Follow the Backup Guide to create a backup of the current SMCP 5.11 management plane.

Remove the existing 1.30-based nodelet cluster:

On all master nodes, clean up the certificate directory:

Download the SMCP 5.10 artifacts and install them:

Update configuration files before deployment:

Edit airctl-config.yaml:
- Update airctlBuildNumber to match the SMCP 5.10 version
Edit nodelet-bootstrap.yaml:
- Update systemImages to use SMCP 5.10 image files
- Set userImages to point to SMCP 5.11 image files
- Add isAirgapped: true for offline installations

Example nodelet-bootstrap.yaml snippet:

Deploy the new 1.27-based nodelet management cluster:

Restore the SMCP 5.10 management plane using the backup created in step 1:

After restoring, you might see errors in the Consul pod saying ACL not found. These errors are harmless and can be ignored.

Therefore, SMCP currently skips the Consul upgrade in the upgrade step and installs the upgraded Consul during the restore process itself.

Check that the DU is in a ready state:

Wait until all components show as ready before proceeding.

If needed, follow the SMCP 5.10 upgrade guide to update the DU components.

Push images for the supported Kubernetes versions (1.27, 1.28, 1.29) to your private registry (if applicable):

To push all new images at once:

Upgrade the host-side components to SMCP 5.10:

After the rollback, confirm the management plane is in a ready state:

Last updated on

Was this page helpful?