Upgrade to a newer version of Kubernetes
Update the patch version
Auto-update of the patch version is not available in Managed Kubernetes clusters:
- on a cloud server with one master node (base cluster) or one worker node;
- a dedicated server.
The upgrade will reinstall all nodes. All data on the boot disk will be deleted.
Kubernetes patch versions contain fixes for bugs and security vulnerabilities in the minor version of Kubernetes. They are compatible with each other within the same minor version.
If patch auto-update is enabled, the cluster will be updated to the latest available patch version during the next cluster maintenance.
You can enable auto-update of patch versions when creating a cluster or for an already created cluster.
- In the dashboard, on the top menu, click Products and select Managed Kubernetes.
- Open the cluster page → Settings tab.
- In the Automation block, enable auto-update of patch versions.
Update the minor version
The minor version upgrade is not available in Managed Kubernetes clusters on a dedicated server.
The upgrade will reinstall all nodes. All data on the boot disk will be deleted.
The minor version of Kubernetes can be updated manually. The master nodes will be updated first, and then the worker nodes will be updated in turn. The upgrade can take from 30 minutes to 12 hours — the duration depends on the size of the cluster. Once started, it will not be possible to stop the upgrade.
- In the dashboard, on the top menu, click Products and select Managed Kubernetes.
- Open the cluster page → Settings tab.
- In the Cluster Settings block, click Show Available Versions.
- Select the version to update.
- Optional: to see the version change history in the official Kubernetes documentation, click Version Change History.
- Click Refresh.