Update a patch Cluster release of a managed cluster¶
Available since 2.23.2
Patch releases are currently not supported for attached MKE clusters, which were not originally deployed by Container Cloud.
A Container Cloud management cluster automatically upgrades to a new Container Cloud patch release, when available. Once done, a newer version of a patch Cluster release becomes available for managed clusters that you update using the Container Cloud web UI.
As compared to a major Cluster release update, a patch release update does not involve any public API or LCM changes, MKE or other major component version bumps, workloads evacuation, or host reboot. A patch cluster update only requires restart of containers running the Container Cloud controllers, Ceph, and StackLight services to update base images with related libraries and apply CVEs with Critical and High severity. The data plane is not affected. For more details, see Patch releases.
If you delay the Container Cloud upgrade and schedule it at a later time as described in Schedule Mirantis Container Cloud upgrades, make sure to schedule a longer maintenance window as the upgrade queue can include several patch releases along with the major release upgrade.
To update a patch Cluster release of a managed cluster:
Log in to the Container Cloud web UI with the
Switch to the required project using the Switch Project action icon located on top of the main left-side navigation panel.
In the Clusters tab, click Upgrade next to the More action icon located in the last column for each cluster where available.
If Upgrade is greyed out, the cluster is in maintenance mode that must be disabled before you can proceed with cluster update. For details, see Disable maintenance mode on a cluster and machine.
If Upgrade does not display, your cluster is up-to-date.
In the Release update window, select the required patch Cluster release to update your managed cluster to.
The release notes for patch Cluster releases are available at Patch releases.
To monitor the cluster readiness, hover over the status icon of a specific cluster in the Status column of the Clusters page.
Once the orange blinking status icon becomes green and Ready, the cluster deployment or update is complete.
You can monitor live deployment status of the following cluster components:
For the OpenStack-based management or regional clusters, the Bastion node IP address status that confirms the Bastion node creation
Installation or upgrade status of all Helm releases
Readiness of the node in a Kubernetes cluster, as reported by kubelet
Readiness of all requested Kubernetes objects
Equality of the requested nodes number in the cluster to the number of nodes having the
Readiness of the cluster OIDC configuration
Health of all StackLight-related objects in a Kubernetes cluster
Readiness of all nodes in a Docker Swarm cluster
Readiness of the Kubernetes API load balancer
Readiness of all machines in the underlying infrastructure (virtual or bare metal, depending on the provider type)
For the history of a cluster deployment or update, refer to Inspect the history of a cluster and machine deployment or update.
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.
For example, you can update from the patch Cluster release 11.7.1 to 11.7.4 at once, but you cannot immediately update from the patch Cluster release 11.7.x to the patch Cluster release 14.0.x because you need to update to the major Cluster release 14.0.0 first. And to obtain the major Cluster release 14.0.0, you should update your cluster to the latest patch Cluster release 11.7.4.