Perform an MKE 4 to MKE 4+ Upgrade

Info

A pre-upgrade backup is automatically generated prior to upgrade initiation.

1. Verify that you have the latest version of the mkectl binary. For information on how to download and install mkectl, refer to Install the MKE 4 CLI.

2. Run the upgrade.

   mkectl upgrade --backup-path <path_to_pre-upgrade_backup>
   

   Important

   Your MKE 4 configuration will mutate during the upgrade to reflect the latest state of the cluster. Thus, you must update your local mke4.yaml configuration file following the upgrade to ensure that it describes the new state. You can do this in one of two ways:

   • Include the --config-out flag with the mkectl upgrade command to automatically refresh the mke4.yaml configuration file:

     mkectl upgrade --upgrade-version <version_to_upgrade_to> --backup-path <path_to_pre-upgrade_backup> --config-out ./mke4.yaml
     

   -- OR --

   • Run mkectl config get > mke4.yaml following the upgrade.

Failed upgrade rollback

If an upgrade from a previous MKE 4 release fails at any stage, the cluster automatically rolls back to the original version using a backup that is created automatically before the upgrade began.

A support bundle is automatically collected as a result of the rollback operation, which you can use to troubleshoot the upgrade procedure.

If the upgrade fails after the Pre Upgrade Backup step, rollback is initiated, restoring the cluster to the state that was captured by that step. If, though, the failure occurs during the Pre Upgrade Checks step or the Pre Upgrade Backup step, no rollback is performed, as no destructive steps have yet taken place.

Rollback runs in reverse order of the upgrade steps that have been executed.