Updating Kubernetes clusters

When a new Kubernetes version becomes available, you can update your Kubernetes cluster to it. An update is non-disruptive for Kubernetes worker nodes, which means that these nodes are updated one by one, with the data availability unaffected. The Kubernetes API will be unavailable during an update, unless high availability is enabled for the master node.

When updating a Kubernetes cluster from version v1.23.5 to v1.24.3, Kubernetes virtual machines are recreated based on a newer Fedora CoreOS image. Such a rolling update is used to preserve the cluster data. Before starting the update, you need to make sure that the compute cluster has enough resources and quotas for at least one extra VM of the largest flavor used by your Kubernetes cluster. If the master and worker node flavors differ, then you should take into account the largest one of them.

Limitations

You cannot update Kubernetes clusters with version 1.15.x to newer versions.
You cannot manage Kubernetes clusters in the self-service panel during an update.

Prerequisites

A Kubernetes cluster is created, as described in Creating and deleting Kubernetes clusters.

To update a Kubernetes cluster

Click a Kubernetes cluster that is marked with the Update available tag.
On the Kubernetes cluster pane, click Update in the Kubernetes version field.
In the Update window, select a Kubernetes version to update to and follow the provided link to read about API resources that are deprecated or obsoleted in the selected version. Then, click Update.
In the confirmation window, click Confirm. The update process will start.

Do not manage Kubernetes virtual machines during the update as it may lead to disruption of the update process and cluster inoperability.