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 |
23.1 series |
22.5 |
22.4 |
22.3 |
||||
|---|---|---|---|---|---|---|---|---|
23.1.4 patch |
23.1.3 patch |
23.1.2 patch |
23.1.1 patch |
23.1 |
||||
Release date |
Jun 05, 2023 |
May 22, 2023 |
May 04, 2023 |
Apr 20, 2023 |
Apr 04, 2023 |
Dec 19, 2022 |
Sept 29, 2022 |
Jun 30, 2022 |
Container Cloud |
2.23.5 - Jun 05, 2023 |
2.23.4 - May 22, 2023 |
2.23.3 - May 04, 2023 |
2.23.2 - Apr 20, 2023 |
2.23.3 - May 04, 2023
2.23.2 - Apr 20, 2023
2.23.1 - Apr 04, 2023
|
2.23.0 - Mar 7, 2023
2.22.0 - Jan 31, 2023
2.21.1 - Dec 19, 2022
|
2.21.0 - Nov 22, 2022
2.20.1 - Sept 29,2022
|
2.20.0 - Sep 05, 2022
2.19.0 - July 27, 2022
2.18.1 - June 30, 2022
|
Deprecated MOSK 0 |
22.5 |
22.5 |
22.5 |
22.5 |
22.5 |
22.4 |
22.3 |
22.2 |
MOSK cluster |
12.7.4 |
12.7.3 |
12.7.2 |
12.7.1 |
12.7.0 |
12.5.0 |
8.10.0 |
8.8.0 |
MKE |
3.5.7 with K8s 1.21 |
3.5.7 with K8s 1.21 |
3.5.7 with K8s 1.21 |
3.5.7 with K8s 1.21 |
3.5.7 with K8s 1.21 |
3.5.5 with K8s 1.21 |
3.4.10 with K8s 1.20 |
3.4.8 with K8s 1.20 |
OpenStack 1 |
Yoga,
Victoria
|
Yoga,
Victoria
|
Yoga,
Victoria
|
Yoga,
Victoria
|
Yoga,
Victoria
|
Yoga,
Victoria
|
Victoria,
Yoga TechPreview
|
Victoria |
Tungsten Fabric |
21.4 |
21.4 |
21.4 |
21.4 |
21.4 |
2011,
21.4 TechPreview
|
2011,
21.4 TechPreview
|
2011 |
Ceph |
Pacific 16.2.11-cve-4 |
Pacific 16.2.11-cve-4 |
Pacific 16.2.11-cve-4 |
Pacific 16.2.11-cve-2 |
Pacific 16.2.11 |
Octopus 15.2.17 |
Octopus 15.2.13 |
Octopus 15.2.13 |
Operating system 2 |
Ubuntu 20.04 Greenfield,
Ubuntu 18.04
|
Ubuntu 20.04 Greenfield,
Ubuntu 18.04
|
Ubuntu 20.04 Greenfield,
Ubuntu 18.04
|
Ubuntu 20.04 Greenfield,
Ubuntu 18.04
|
Ubuntu 20.04 Greenfield,
Ubuntu 18.04
|
Ubuntu 20.04 Greenfield,
Ubuntu 18.04
|
Ubuntu 20.04 Greenfield,
Ubuntu 18.04
|
Ubuntu 18.04 |
Linux kernel 3 |
5.4.0-137-generic |
5.4.0-137-generic |
5.4.0-137-generic |
5.4.0-137-generic |
5.4.0-137-generic |
5.4.0-125-generic |
5.4.0-122-generic |
5.4.0-109-generic |
- 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.
- 1
The LTS duration of an OpenStack version is two years. For support timeline for different OpenStack versions, refer to OpenStack support cycle.
- 2
The implementation and verification of the Ubuntu 18.04 to 20.04 upgrade procedure has been scheduled for the 2023 year.
- 3
Updating the kernel of the host operating system requires rebooting of the cluster nodes as described in Step 4. Reboot the nodes with optional instance migration. Make sure you switch to the kernel version supported by the target MOSK release to complete the cluster update.
Upgrade paths¶
Component |
From |
To |
Procedure |
|---|---|---|---|
Container Cloud |
N version |
N+1 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 major cluster release |
N major version |
N+1 major 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 to a major release version for details. 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. |
MOSK patch cluster release |
N patch version |
M patch 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 to a patch release version New for details. You can skip a number of patch releases and update to the latest one. Though, if you start receiving the patch releases, you should always apply the latest patch release in the series to be able to update to the following major release. |
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 |
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. |