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.

Distribution upgrade of an operating system (OS) is implemented for management and MOSK clusters.

For management clusters, an OS distribution upgrade occurs automatically as part of cluster update and requires machines reboot. The upgrade workflow is as follows:

  1. The distribution ID value is taken from the id field of the distribution from the allowedDistributions list in the spec of the ClusterRelease object.

  2. The distribution that has the default: true value is used during update. This distribution ID is set in the spec:providerSpec:value:distribution field of the Machine object during cluster update.

For MOSK clusters, an in-place OS distribution upgrade should be performed between cluster updates. This scenario implies a machine cordoning, draining, and reboot. Upgrading all nodes at once is not mandatory. You can upgrade them individually or in small batches, depending on time constraints in the maintenance window.

The table below illustrates the correlation between the cluster updates and upgrade to Ubuntu 24.04 to help you effectively plan and perform the upgrade.

Correlation between cluster updates and upgrade to Ubuntu 24.04

Management cluster version

MOSK cluster version

Default Ubuntu version

Key impact

Action required

2.31.0

26.1

24.04

No impact

Strongly recommended to upgrade Ubuntu on all MOSK cluster nodes during the course of the MOSK 26.1.x series. 0

The management cluster update to 2.32.0 will be blocked if at least one node of any related MOSK cluster is running Ubuntu 22.04.

2.30.0
25.1.x
25.2
22.04
24.04 1

No impact

Management cluster nodes are automatically upgraded to Ubuntu 24.04 during cluster update to MOSK management 2.30.0 (Cluster release 20.0.0).

Upgrade of MOSK clusters to Ubuntu 24.04 will become available in the following release.
0

Upgrading all nodes at once is not mandatory. You can upgrade them individually or in small batches, depending on time constraints in the maintenance window.

1

Ubuntu 22.04 on MOSK clusters and Ubuntu 24.04 on management clusters.

To upgrade an OS distribution on MOSK between releases:

Caution

A machine reboot occurs automatically during distribution update.

  1. Open the required Machine object for editing.

  2. In spec:providerSpec:value:distribution, set the required ID of the new OS version. For example, ubuntu/noble.

    For description of the Machine object fields, see Machine resource.

    The machine reboot occurs automatically after completion of deployment phases.

  3. Once the distribution upgrade completes, verify that currentDistribution matches the distribution value previously set in the object spec. For description of the status fields, see Machine status.

  4. Repeat the procedure with the remaining machines.

  5. Strongly recommended. Back up MKE as described in Create backups of Mirantis Kubernetes Engine.

    Since the procedure above modifies the cluster configuration, a fresh backup is required to restore the cluster in case further reconfigurations fail.

See also

Cluster update