Upgrade an existing MKE 4 cluster#
Important
Starting with MKE 4.2.0, MKE 4.1.2 and earlier clusters must first be upgraded to MKE 4.1.3 or MKE 4.1.5 before they can be upgraded to the MKE 4.2.0 or later. For more information, refer to the Upgrade an existing MKE 4 cluster documentation for the MKE 4 version you are running.
Typically, each MKE 4 CLI (mkectl) version is tethered to a particular MKE 4 release and should only be used with that release. Thus, for example, you must use mkectl x.y.1 with MKE 4 release x.y.1 and not with MKE 4 release x.y.2. An exception to this, though, is when you upgrade MKE 4 to a later release, wherein you should use the mkectl version that aligns with the target MKE 4 release.
The current upgrade paths to MKE 4.2.0 for existing MKE 4 clusters are detailed below:
| Source release | Target release | mkectl version required |
|---|---|---|
| 4.1.3 | 4.2.0 | 4.2.0 |
| 4.1.5 | 4.2.0 | 4.2.0 |
Important
- You cannot change the registries once a cluster is operational.
- Before you upgrade to MKE 4.2.0, Mirantis suggests that you manually upgrade any CRDs that
were made available following the introduction of
prometheus-operatorv0.86.2. For more information, refer to Upgrade Monitoring CRDs.