The OVHcloud Managed Kubernetes service provides you Kubernetes clusters without the hassle of installing or operating them. In this guide, we cover how you can easily upgrade your cluster to the next minor version of Kubernetes.
On OVHcloud Managed Kubernetes, we have deployed an Upgrade to the next minor version of Kubernetes feature to upgrade your cluster from one version to the next (e.g., 1.13 to 1.14).
- An OVHcloud Managed Kubernetes cluster
Important information on the upgrading process
Before you launch the upgrade, please back up your cluster’s configuration, and check that your worker tools are compatible with this new version.
The upgrading process will try to do a rolling upgrade. Please ensure that your cluster includes enough worker nodes to allow for a rolling upgrade.
To minimize downtime for your pods and your overall service, we will drain each of your nodes, only moving on to the next node when the current one is functional (i.e., when the status changes to ‘Ready’). Your admin components and server API will also be updated.
This operation usually takes around five minutes per node in your cluster, but that can vary depending on your cluster type and size.
Once the update has been performed, you cannot revert to the previous version.
Step 1 - Ask for a minor version upgrade on the OVHcloud Control Panel
Log into the OVHcloud Control Panel. Go to the
Public Cloudsection and select the Public Cloud project concerned.
Access the administration UI for your OVHcloud Managed Kubernetes clusters by clicking on
Managed Kubernetes Servicein the left-hand menu.
Click on the right end button of your Kubernetes cluster and choose
On the Management section, click on
Upgrade to the next minor version.
Note: Your security policy must be set at least to “Minimum unavailability”. Otherwise, the upgrade will fail.
Step 2 - Wait for the upgrading to end
The upgrading process can take several minutes (around five minutes per node in your cluster). During that time, a message on the OVHcloud Control Panel warns you that the cluster is being upgraded: