Skip to main content
You can configure the Kubernetes version that is used on your Managed Kubernetes clusters and node groups.
  • Clusters: The Kubernetes version is used for control plane components. It is required when creating a cluster.
  • Node groups: The Kubernetes version is used for node components. It is optional when creating a node group. By default, a node group uses the same Kubernetes version as its parent cluster. A node group cannot have a higher version than the cluster.

​
Available Kubernetes versions

The following Kubernetes versions are currently supported for clusters and node groups:
  • 1.32: Recommended. New clusters use this version.
  • 1.31 and 1.30: Not recommended (they reached end of life). These versions are supported for clusters created earlier, but we recommend upgrading to the newest version.
For the version deprecation policy and end-of-life timeline, see Kubernetes® version deprecation policy in Managed Service for Kubernetes.

​
Upgrading Kubernetes version

You can upgrade a cluster to a newer Kubernetes version manually; automatic upgrade is not supported. To do so, upgrade the control plane first and then the node groups. Node groups are not upgraded automatically together with the cluster, even if you created the cluster and node groups with the same version. Consider possible downtimes during the upgrade:
  • If the control plane is not highly available—that is, it has only one etcd store—the cluster becomes unavailable during the control plane upgrade.
  • When you upgrade a node group, the nodes are replaced one by one, according to the node group’s deployment strategy. If .spec.strategy.max_unavailable is greater than 0, some nodes might be unavailable during the upgrade. You can check the node group specifications by using the following command: 
    nebius mk8s node-group get --id <node_group_ID>
See detailed instructions in Setting and upgrading Kubernetes® versions in Managed Service for Kubernetes.