Update a MOS cluster

Once a Mirantis Container Cloud management cluster automatically upgrades to a new available Container Cloud release version, a newer version of a Cluster release becomes available for MOS managed clusters.

This section instructs you on how to update your MOS cluster using the Container Cloud web UI.

Note

The Tungsten Fabric update is part of the MOS managed cluster release update and does not require any additional manual steps.

Caution

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 update a MOS cluster:

  1. Set the maintenance flag for Ceph:

    Note

    Starting from the MOS 21.4 to 21.5 update, skip this step since it is automated. The maintenance flag is deprecated and will be removed from KaasCephCluster.

    1. Open the KaasCephCluster CR for editing:

      kubectl edit kaascephcluster
      
    2. Enable the maintenance flag:

      spec:
        cephClusterSpec:
          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.

  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 view the update status, verify the cluster status on the Clusters page. Once the orange blinking dot near the cluster name disappears, the update is complete.

  7. Disable the maintenance flag for Ceph from the KaasCephCluster CR once the update is complete and all nodes are in the Ready status:

    Note

    Starting from the MOS 21.4 to 21.5 update, skip this step since it is automated. The maintenance flag is deprecated and will be removed from KaasCephCluster.

    spec:
      cephClusterSpec:
        maintenance: false
    

Note

In rare cases, after a managed cluster update, 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.

Note

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