Mirantis Container Cloud (MCC) becomes part of Mirantis OpenStack for Kubernetes (MOSK)!

Starting with MOSK 25.2, the MOSK documentation set will cover all product layers, including MOSK management (formerly MCC). This means everything you need will be in one place. The separate MCC documentation site will be retired, so please update your bookmarks for continued easy access to the latest content.

Cluster update

Updating a MOSK cluster ensures that the system remains secure, efficient, and up-to-date with the latest features and performance improvements, as well as receives fixes for the known CVEs. This section provides comprehensive details and step-by-step procedures to guide you through the process of updating your cluster.

Cluster updates in MOSK encompass both management cluster and MOSK cluster updates:

Update type

Description

Management cluster update

The management cluster update is performed automatically as long as the release of each managed cluster has either supported or deprecated status in the new version of MOSK management. In case any of the clusters managed by MOSK management is about to get an unsupported status as a result of an update, the MOSK management cluster updates will get blocked till the cluster gets to a later release.

For the cluster release statuses, refer to Cluster support statuses.

Cluster major update

Major cluster update is initiated by a cloud operator through the MOSK management console. The update procedure is automated and covers all the life cycle management modules of the cluster that include OpenStack, Tungsten Fabric, Ceph, and StackLight. Refer to Update to a major version for the procedure.

Version-specific considerations

Before the MOSK 24.1 series, if between the major releases you apply at least one patch release belonging to the N series, you should obtain the last patch release in the series to be able to update to the N+1 major release version.

Since MOSK 24.1.5, the product introduces a new approach to cluster updates. For details, refer to Cluster update scheme and Update schemes comparison.

Cluster patch update

Patch cluster update is initiated by a cloud operator through the MOSK management console. The update procedure is automated and covers all the life cycle management modules of the cluster that include OpenStack, Tungsten Fabric, Ceph, and StackLight. Refer to Update to a patch version for the procedure.

Version-specific considerations

Since MOSK 24.1.5, the product introduces a new approach to cluster updates. For details, refer to Cluster update scheme and Update schemes comparison.