Kubernetes versions and updates in Managed Service for Kubernetes
You can choose Kubernetes version for your cluster when creating or editing it, configure automatic updates, and perform manual updates.
The Kubernetes version you choose is used both for master (control plane) and nodes.
List of available Kubernetes versions
The following Kubernetes versions are available in Managed Service for Kubernetes:
- Kubernetes 1.26
- Kubernetes 1.27
- Kubernetes 1.28
You can also get the up-to-date list of available versions following the guide.
Updates
When an update appears, the corresponding information is displayed in the management console. You can install updates automatically or manually.
-
Automatic updates are installed in the specified period of time with no interaction from the user. They cannot be turned off.
Updates are triggered and should be completed within the specified period. In some cases, when updating a node group, an update may continue beyond such period.
Automatic updates include: new Managed Service for Kubernetes functions, improvements, and fixes, as well as Kubernetes component fixes.
Alert
If Kubernetes version support ends, minor Kubernetes versions get updated as well.
-
Manual updates can be initiated by the user at any time.
These include Kubernetes minor version updates.
Read more about Kubernetes version support termination and the Kubernetes cluster component update process.
Kubernetes version support termination
When an old version of Kubernetes is no longer supported after an update:
- The master can't be updated automatically, update it manually.
- Minor versions (for example, from 1.26 to 1.27) must be updated manually.
- Node groups are updated automatically.
Updating Kubernetes cluster components
The update process is different for masters and node groups.
Master
For more information, see Updating a cluster.
Node group
Update node group algorithm:
- An updated node is created with the configuration specified for the entire node group.
- All pods are evicted from one of the old nodes based on the pre-defined PodDisruptionBudgets policy. Then the node is deleted.
- The process is repeated until all nodes in the group are updated.
This ensures that the number of nodes in the node group never falls below the number specified when the group is created.
Certificates
In accordance with the safety recommendations, cluster and node group certificates
- If automatic updates are enabled, certificates are updated automatically at every cluster or node group update.
- If automatic updates are disabled, a certificate update will be forced a week before they expire.
For more information about updating certificates, see the Kubernetes documentation