Skip to content

Upgrading an existing MKE 4k cluster#

Typically, each MKE 4k CLI (mkectl) version is tethered to a particular MKE 4k release and should only be used with that release. Thus, for example, you must use mkectl x.y.1 with MKE 4k release x.y.1 and not with MKE 4k release x.y.2. An exception to this, though, is when you upgrade MKE 4k to a later release, wherein you should use the mkectl version that aligns with the target MKE 4k release.

The current upgrade paths for MKE 4k clusters are detailed below:

Source release Target release mkectl version required
4.1.0 4.1.2 4.1.2
4.1.1 4.1.2 4.1.2

Info

As MKE 4.1.0 is built on an alpha version of k0rdent, upgrading from that MKE 4k release involves a complete reinstallation of MKE 4k and k0rdent, resulting in a more prolonged upgrade process.

Important

You cannot change the registries once a cluster is operational.

To upgrade your MKE 4k cluster:

  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 4k CLI.

  2. Back up MKE 4k prior to initiating the upgrade.

    Info

    If you do not provide a path to an MKE 4k backup as part of the mkectl upgrade command, mkectl automatically generates a pre-upgrade backup prior to initiating the upgrade.

  3. Run the upgrade.

    mkectl upgrade --upgrade-version <version_to_upgrade_to> \
               --etcd-snapshot-path <path_to_pre-upgrade_snapshot>