Skip to content
Due to upgrade issues with the Envoy gateway and the offline installation environments, upgrading to MKE 4k 4.1.3 is not recommended. These issues will be fixed in a future release. For version 4.1.3, Mirantis only supports fresh installations.

Obtain the version of the current MKE 4k cluster#

The method for determining the version of your MKE 4k cluster depends on whether the cluster is a standalone cluster or a Mothership cluster with child cluster deployemnts.

To obtain the version of a standalone MKE 4k cluster, run the following command:

kubectl -n mke get mkeconfig mke -o jsonpath='{.spec.version}'

To obtain the version of a Mothership MKE 4k cluster with child cluster deployments:

For the Mothership:

  1. Load the Kubernetes configuration:

    export KUBECONFIG=~/.mke/mke.kubeconf

  2. List the control plane nodes:

    kubectl get nodes | grep control-plane

    Example result:

    ip-172-31-50-200.us-west-2.compute.internal    Ready    control-plane   7h8m   v1.32.6+k0s

  3. Obtain the MKE 4k version:

    kubectl get node ip-172-31-50-200.us-west-2.compute.internal  -o yaml | yq '.metadata.labels.mke/version'

    Example result:

    v4.1.3

For each child cluster:

  1. Load the Kubernetes configuration:

    export KUBECONFIG="$(pwd)/<childcluster-name>-kubeconfig"

  2. List the control plane nodes:

    kubectl get nodes | grep control-plane

    Example result:

    <childcluster-name>-cp-0             Ready    control-plane   5h30m   v1.32.8+k0s
<childcluster-name>-cp-1             Ready    control-plane   5h29m   v1.32.8+k0s
<childcluster-name>-cp-2             Ready    control-plane   5h28m   v1.32.8+k0s

  3. Obtain the MKE 4k version:

    kubectl get node <childcluster-name>-cp-0 -o yaml | yq '.metadata.labels.mke/version'

    Example result:

    v4.1.3