Update notes

This section describes the specific actions you as a Cloud Operator need to complete to accurately plan and successfully perform your Mirantis OpenStack for Kubernetes (MOSK) cluster update to the version 24.3. Consider this information as a supplement to the generic update procedure published in Operations Guide: Update a MOSK cluster.

Cluster update schema

According to the new cluster update schema introduced in the product in the MOSK 24.2 series, you can update to the 24.3 version from the following cluster versions:

  • 24.2 (released on July 02, 2024)

  • 24.2.2 (released on September 16, 2024)

For the detailed cluster update schema, refer to Managed cluster update schema.

Features

The MOSK cluster will obtain the newly implemented capabilities automatically with no significant impact on the update procedure.

Update impact and maintenance windows planning

The following table provides details on the update impact on a MOSK cluster.

Impact during update to MOSK 24.3

Updated component

Impact on cloud users

Impact on cloud workloads

OpenStack and Tungsten Fabric

  • ~1% of read operations on cloud API resources may fail

  • ~8% of create and update operations on cloud API resources may fail

Open vSwitch networking - interruption of the North-South connectivity, depending on the type of virtual routers used by a workload:

  • Distributed (DVR) routers - no interruption

  • Non-distributed routers, High Availability (HA) mode - interruption up to 1 minute, usually less than 5 seconds

  • Non-distributed routers, non-HA mode - interruption up to 10 minutes

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 0

0

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.

To properly plan the update maintenance window, use the following documentation:

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.

Pay special attention to [47602] Failed designate-zone-setup job blocks cluster update. Before performing the cluster update, verify the DNS service (OpenStack Designate) for any created Top-Level Domains (TLDs). If TLDs are present but the test TLD is missing, create test according to the known issue description.

Post-update actions

Upgrade Ubuntu to 22.04

MOSK 24.3 release series is the last one to support Ubuntu 20.04 as the host operating system. Ubuntu 20.04 reaches end-of-life in April 2025. Therefore, Mirantis encourages all MOSK users to upgrade their clusters to Ubuntu 22.04 as soon as possible after getting to MOSK 24.3.

A host operating system upgrade requires reboot of the servers and can be performed in small batches. For the detailed procedure of the Ubuntu upgrade, refer to Upgrade an operating system distribution.

Warning

Update of management or MOSK clusters running Ubuntu 20.04 will not be possible in the following major product version.

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.

Start using new API for Tungsten Fabric configuration (TFOperator v2)

Since MOSK 24.3, the v2 TFOperator custom resource becomes the default and the only way to manage the configuration of Tungsten Fabric cluster. During update to MOSK 24.3, the old v1alpha1 TFOperator custom resource will get automatically converted to version v2.

Note

The v1alpha1 TFOperator custom resource remains in the cluster but is no longer reconciled and will be automatically removed with the next major cluster update.

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 managed clusters, you can perform the backup after the Container Cloud 2.29.0 release date but before updating them to MOSK 25.1.