Skip to content

Upgrade from MKE 3.7, 3.8, or 3.9#

Warning

Starting with MKE 4.2.0, only MKE 3.9.x clusters can be upgraded to MKE 4.2.0 and later. If you are running MKE a 3.7.15+ or 3.8.x cluster you must first upgrade to MKE 3.9.x before upgrading to the latest version of MKE 4.

Important

In the event of upgrade failure, the cluster will roll back to your previous MKE 3 configuration. Should this occur, Mirantis recommends that you retain the upgrade logs from the terminal.

Note

You cannot upgrade MKE 3 clusters running Calico CNI with eBPF dataplane to MKE 4.

Comprehensive information is offered herein on how to upgrade your existing MKE 3.9 cluster to MKE 4.

Following a successful upgrade:

  • Any swarm workloads will no longer exist.
  • For the admin user, the kubeconfig file is present in the ~/.mke/ directory of the machine upon which the MKE 4 CLI (mkectl) command was executed. For other users, the admin can create their kubeconfig files.
  • The UCP Controller API will no longer be active or supported, and thus the MKE 3 client bundle will become invalid for MKE 4.
  • Only etcd v3 API data will be available. The etcd v2 data in MKE 3 exists solely to support Swarm workloads, which MKE 4 does not support, and thus that data is not carried over.

  • The terminal prints a summary of the process, for example::

    Upgrade Summary
---------------
Configuration file
---------------
All MKE 3 TOML settings were successfully converted into MKE 4 YAML settings.
Authentication
---------------
Users found in the MKE3 cluster: 1
All users were upgraded to the MKE 4 cluster successfully.
Authorization
---------------
Organizations found in the MKE3 cluster: 1
Teams found in the MKE3 cluster: 0
All organizations and teams were translated to aggregated roles in the MKE 4
cluster successfully.
Ports
---------------
The following MKE 3 ports are no longer used by MKE 4 and (unless otherwise needed) may be made unavailable on all nodes: [2377,6444,7946,9055,12376,12378,12379,12380,12381,12382,12383,12384,12385,12386,12387,12388,12389,12391,12392,179,12390,2376,443]
MCR
---------------
MCR may safely be uninstalled
MKE3 Cleanup
---------------
MKE 3.9.3 was uninstalled from the cluster successfully.

Warning

Your MKE 3.9 system will be completely unavailable during the upgrade process. Cluster access will be restored only once the upgrade is complete.

The upgrade period depends on the size of your cluster. You can track the progress of your upgrade by way of the terminal, which displays step-by-step logs on the current state of upgrade.