Update a managed cluster

A Mirantis Container Cloud management cluster automatically upgrades to a new available Container Cloud release version that supports new Cluster releases. Once done, a newer version of a Cluster release becomes available for managed clusters that you update using the Container Cloud web UI.


Before upgrading your managed cluster with StackLight deployed in HA mode to the latest Cluster release, follow the steps provided in Upgrade managed clusters with StackLight deployed in HA mode.


Make sure to update the Cluster release version of your managed cluster before the current Cluster release version becomes unsupported by a new Container Cloud release version. Otherwise, Container Cloud stops auto-upgrade and eventually Container Cloud itself becomes unsupported.


  • To silence StackLight alerts before performing the update, see Silence alerts.

  • All iam-proxy services in the StackLight namespace are restarted during update. This causes a short downtime for the web UI access to StackLight services, although all services themselves, such as Kibana or Grafana, continue working.

This section describes how to update a managed cluster of any provider type using the Container Cloud web UI.

To update a managed cluster:

  1. For bare metal and Equinix Metal clusters, set the maintenance flag for Ceph:


    Starting from Container Cloud 2.11.0 to 2.12.0 upgrade, skip this step. The maintenance flag function is set up programmatically and the flag itself is deprecated since Container Cloud 2.12.0.

    1. Open the KaasCephCluster CR for editing:

      kubectl edit kaascephcluster
    2. Enable the maintenance flag:

          maintenance: true
  2. Log in to the Container Cloud web UI with the writer permissions.

  3. Switch to the required project using the Switch Project action icon located on top of the main left-side navigation panel.

  4. In the Clusters tab, click More action icon in the last column for each cluster and select Update cluster where available.

  5. In the Release Update window, select the required Cluster release to update your managed cluster to.

    The Description section contains the list of components versions to be installed with a new Cluster release. The release notes for each Container Cloud and Cluster release are available at Mirantis Container Cloud releases and Cluster releases (managed).

  6. Click Update.

    Before the cluster update starts, Container Cloud performs a backup of MKE and Docker Swarm. The backup directory is located under:

    • /srv/backup/swarm on every Container Cloud node for Docker Swarm

    • /srv/backup/ucp on one of the controller nodes for MKE

    To monitor the cluster readiness, hover over the status icon of a specific cluster in the Status column of the Clusters page.

    Once the orange blinking status icon is green and Ready, the cluster deployment or update is complete.

    You can monitor live deployment status of the following cluster components:




    For the OpenStack and AWS-based clusters, the Bastion node IP address status that confirms the Bastion node creation


    Installation or upgrade status of all Helm releases


    Readiness of the node in a Kubernetes cluster, as reported by kubelet


    Readiness of all requested Kubernetes objects


    Equality of the requested nodes number in the cluster to the number of nodes having the Ready LCM status


    Readiness of the cluster OIDC configuration


    Health of all StackLight-related objects in a Kubernetes cluster


    Readiness of all nodes in a Docker Swarm cluster


    Readiness of the Kubernetes API load balancer


    Readiness of all machines in the underlying infrastructure (virtual or bare metal, depending on the provider type)

  7. For bare metal and Equinix Metal clusters, disable the maintenance flag for Ceph from the KaasCephCluster CR once the update is complete and all nodes are in the Ready status:


    Starting from Container Cloud 2.11.0 to 2.12.0 upgrade, skip this step. The maintenance flag function is set up programmatically and the flag itself is deprecated since Container Cloud 2.12.0.

        maintenance: false


In rare cases, after a managed cluster upgrade, Grafana may stop working due to the issues with helm-controller.

The development team is working on the issue that will be addressed in one of the following releases.


MKE and Kubernetes API may return short-term 50x errors during the upgrade process. Ignore these errors.