Release Compatibility Matrix NEW

The Mirantis OpenStack for Kubernetes (MOS) release compatibility matrix describes the cloud configurations that have been supported by the product over the course of its lifetime and the path a MOS cloud can take to move from an older configuration to a newer one.

For each MOS release, the document outlines the versions of the product major components, the valid combinations of these versions, and the way every component must be updated or upgraded.

For a more comprehensive list of the product subcomponents and their respective versions included in each MOS release, refer to MOS Release Notes, or use the Releases section in the Container Cloud UI or API.

Compatibility matrix

The following table outlines the compatibility matrix of the most recent MOS releases and their major components in conjunction with Container Cloud and Cluster releases.

MOS

21.6

21.5

21.4

21.3

21.2

MOS release date

Nov 11, 2021

Oct 05, 2021

Sept 01, 2021

June 15, 2021

Apr 22, 2021

Container Cloud

2.13.1 - Nov 11, 2021

2.13 - Oct 28, 2021,
2.12 - Oct 05, 2021

2.11.0 - Sept 01, 2021

2.10.0 - July 07, 2021,
2.9.0 - June 15, 2021
2.8.0 - May 18, 2021,
2.7.0 - Oct 28, 2021

Deprecated MOS 0

21.5

21.4

21.3

21.2

21.1

MOS cluster

6.20.0

6.19

6.18

6.16

6.14

MKE

3.3.12 K8s 1.18

3.3.12 K8s 1.18

3.3.6 K8s 1.18

3.3.6 K8s 1.18

3.3.6 K8s 1.18

OpenStack

Victoria LTS

Victoria LTS,
Ussuri
Victoria LTS,
Ussuri
Victoria LTS,
Ussuri
Victoria LTS,
Ussuri

Tungsten Fabric

2011 LTS

2011 LTS,
5.1
2011 TechPrev,
5.1
2011 TechPrev,
5.1

5.1

Ceph

Octopus 15.2.13

Octopus 15.2.13

Octopus 15.2.13

Nautilus 14.2.19

Nautilus 14.2.12

0

Mirantis Container Cloud will update itself automatically as long as the release of each managed cluster has either supported or deprecated status in the new version of Container Cloud.

A deprecated cluster release becomes unsupported in one of the following Container Cloud releases. Therefore, we strongly recommend that you update your deprecated MOS clusters to the latest supported version as described in Upgrade paths.

Upgrade paths

Component

From

To

Procedure

Container Cloud

N minor version

N+1 minor version

Mirantis Container Cloud will update itself automatically as long as the release of each managed cluster has either supported or deprecated status in the new version of Container Cloud.

In case, any of the clusters managed by Container Cloud is about to get an unsupported status as a result of an update, the Container Cloud updates will get blocked till the cluster gets to a later release.

For the cluster release statuses, see Container Cloud documentation: Cluster releases (managed).

MOS and MOS cluster release

N minor version

N+1 minor version

A cloud operator initiates an update of a MOS cluster using the Container Cloud UI. The update procedure is automated and covers all the life cycle management modules of the cluster that include OpenStack, Tungsten Fabric, Ceph, and StackLight.

See Update a MOS cluster for details.

OpenStack

Ussuri

Victoria

Available since MOS 21.3

A cloud operator uses the MOS life cycle management API to upgrade OpenStack.

See Upgrade OpenStack for details

Tungsten Fabric

5.1

2011

Available since MOS 21.5

A cloud operator uses the MOS life cycle management API to upgrade Tungsten Fabric deployments. It is recommended to upgrade a corresponding OpenStack deployment first.

See Upgrade Tungsten Fabric to 2011 for details.

Ceph

N

N+1

Ceph cluster is updated and upgraded automatically as a part of the MOS cluster update.