Update notes¶
This section describes the specific actions you need to complete to accurately plan and successfully perform the update. Consider this information as a supplement to the generic update procedures published in Operations Guide: Cluster update.
Cluster update schema¶
You can update to the 24.3.3 version from the following cluster versions:
Patch update: 24.3.1 (January 06, 2025) or 24.3.2 (February 03, 2025)
Major update: 24.3 (October 16, 2024)
For the detailed cluster update schema, refer to Managed cluster update schema.
Patch update impact and maintenance windows planning¶
The following table provides details on the impact of a MOSK cluster update to a patch release within the 24.3 series.
Note
For the detailed workflow of update to a patch release, refer to Update to a patch version.
Updated component |
Impact on cloud users |
Impact on cloud workloads |
|---|---|---|
OpenStack and Tungsten Fabric |
|
Open vSwitch networking - interruption of North-South connectivity, depending on the type of virtual routers used by a workload:
Tungsten Fabric networking - no impact |
Ceph |
~1% of read operations on object storage API may fail |
IO performance degradation for Ceph-backed virtual storage devices. Pay special attention to the known issue 50566 that may affect the maintenance window. |
Host OS components |
No impact |
No impact |
- 0(1,2)
You can bypass updating components of the cloud data plane to avoid the network downtime during Update to a patch version. By using this technique, you accept the risk that some security fixes may not be applied.
Major update impact and maintenance windows planning¶
The following table provides details on the update impact on a MOSK cluster.
Updated component |
Impact on cloud users |
Impact on cloud workloads |
|---|---|---|
OpenStack and Tungsten Fabric |
|
Open vSwitch networking - interruption of the North-South connectivity, depending on the type of virtual routers used by a workload:
Tungsten Fabric networking - no impact |
Ceph |
~1% of read operations on object storage API may fail |
IO performance degradation for Ceph-backed virtual storage devices |
Host OS components |
No impact |
Instance network connectivity interruption up to 5 minutes |
Host OS kernel |
No impact |
Restart of instances due to the hypervisor reboot 1 |
- 1
Host operating system needs to be rebooted for the kernel update to be applied. Configure live-migration of workloads to avoid the impact on the instances running on a host.
Known issues during the update¶
Before updating the cluster, be sure to review the potential issues that may arise during the process and the recommended solutions to address them, as outlined in Update known issues.
Pre-update actions¶
Update MOSK clusters to Ubuntu 22.04¶
Management cluster update to Container Cloud 2.29.1 will be blocked if at least one node of any related MOSK cluster is running Ubuntu 20.04.
Therefore, ensure that every node of your MOSK clusters are running Ubuntu 22.04 to unblock management cluster update to Container Cloud 2.29.1 and MOSK cluster update to 24.3.3.
For the update procedure, refer to Upgrade an operating system distribution.
Caution
Usage of third-party software, which is not part of Mirantis-supported configurations, for example, the use of custom DPDK modules, may block upgrade of an operating system distribution. Users are fully responsible for ensuring the compatibility of such custom components with the latest supported Ubuntu version.
Migrate container runtime from Docker to containerd¶
Since 24.3.1, MOSK introduces the new container runtime for the underlying Kubernetes cluster - containerd. The migration from Docker to containerd in 24.3.3 is still optional and requires node cordoning and draining.
If you decide to start using containerd and have not yet upgraded to Ubuntu 22.04, Mirantis highly recommends that these two changes be applied simultaneously to every node to minimize downtime for cloud workloads and users. In this case, ensure that all cluster machines are updated at once during the same maintenance window to prevent machines from running different container runtimes.
For the migration procedure, refer to Migrate container runtime from Docker to containerd.
Note
In MOSK 24.3.x, the default container runtime remains Docker for greenfield deployments. Support for greenfield deployments based on containerd is added in Container Cloud 2.29.0 (Cluster release 16.4.0) for management clusters and in MOSK 25.1 for MOSK clusters.
Back up custom Grafana dashboards¶
In MOSK 25.1 and Container Cloud 2.29.0, Grafana will be updated to version 11 where the following deprecated Angular-based plugins will be automatically migrated to the React-based ones:
Graph (old) -> Time Series
Singlestat -> Stat
Stat (old) -> Stat
Table (old) -> Table
Worldmap -> Geomap
This migration may corrupt custom Grafana dashboards that have Angular-based panels. Therefore, if you have such dashboards, back them up and manually upgrade Angular-based panels during the course of MOSK 24.3 and Container Cloud 2.28.x (Cluster releases 17.3.x and 16.3.x) to prevent custom appearance issues after plugin migration in Container Cloud 2.29.0 and MOSK 25.1.
Note
All Grafana dashboards provided by StackLight are also migrated to React automatically. For the list of default dashboards, see View Grafana dashboards.
Warning
For management clusters that are updated automatically, it is important to prepare the backup before Container Cloud 2.29.0 is released. Otherwise, custom dashboards using Angular-based plugins may be corrupted.
For MOSK clusters, you can perform the backup after the Container Cloud 2.29.0 release date but before updating them to MOSK 25.1.