Release Compatibility Matrix¶
The Release Compatibility Matrix describes the cloud configurations that have been supported by the product over the course of its lifetime and the path a MOSK cloud can take to move from an older configuration to a newer one.
For each MOSK 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 MOSK release, refer to 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 MOSK releases and their major components in conjunction with Container Cloud and Cluster releases.
MOSK |
22.2 |
22.1 |
21.6 |
21.5 |
|---|---|---|---|---|
MOSK release date |
Apr 14, 2022 |
Feb 23, 2022 |
Nov 11, 2021 |
Oct 05, 2021 |
Container Cloud |
2.17.0 - May 11, 2022
2.16.1 - Apr 14, 2022
|
2.16.0 - Mar 31, 2022
2.15.1 - Feb 23, 2022
|
2.15 - Jan 31, 2022
2.14 - Dec 07, 2021
2.13.1 - Nov 11, 2021
|
2.13 - Oct 28, 2021,
2.12 - Oct 05, 2021
|
Deprecated MOSK 0 |
22.1 |
21.6 |
21.5 |
21.4 |
MOSK cluster |
8.6.0 |
8.5.0 |
6.20.0 |
6.19 |
MKE |
3.4.7
K8s 1.20
|
3.4.6
K8s 1.20
|
3.3.12
K8s 1.18
|
3.3.12
K8s 1.18
|
OpenStack |
Victoria LTS |
Victoria LTS |
Victoria LTS |
Victoria LTS,
Ussuri
|
Tungsten Fabric |
2011 LTS |
2011 LTS |
2011 LTS |
5.1 |
Ceph |
Octopus 15.2.13 |
Octopus 15.2.13 |
Octopus 15.2.13 |
Octopus 15.2.13 |
- 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 MOSK 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). |
MOSK and MOSK cluster release |
N minor version |
N+1 minor version |
A cloud operator initiates an update of a MOSK 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 MOSK cluster for details. |
OpenStack |
Ussuri |
Victoria |
A cloud operator uses the MOSK life-cycle management API to upgrade OpenStack. See Upgrade OpenStack for details |
Tungsten Fabric |
5.1 |
2011 |
Available since MOSK 21.5 A cloud operator uses the MOSK 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 MOSK cluster update. |