Release notes in Managed Kubernetes

2026

June

added support for user data in clusters on dedicated servers. Learn more about user data in the guide User data in Managed Kubernetes node groups;
updated the list of applications that can be installed in a Managed Kubernetes cluster via the Control Panel — added the option to install the Envoy Gateway application and removed the option to install the NGINX Ingress Controller application.

May

added a new cluster type: a fault-tolerant multi-zone cluster. Available only in the multi-zone pool ru-6. Learn more about cluster types in the section Cluster types of the guide Managed Kubernetes product description;
added to audit logs the events of the mks service related to the Envoy Gateway application.

April

updated the list of supported Kubernetes versions;
updated the containerd configuration storage format on worker nodes — the configuration is now stored in the /etc/containerd/certs.d/docker.io/ directory in the hosts.toml file. This allows adding directories for private registries and configuring them separately, for example, specifying a CA certificate for self-signed TLS or disabling certificate verification. Learn more about configuring containerd registries via the hosts.toml file in the containerd documentation on GitHub.

For Managed Kubernetes clusters, version 1.31 and higher, the new containerd configuration storage format is applied by default when a cluster is created. In existing clusters, the changes will be applied automatically upon worker node reinstallation or when creating a new node group.

March

added to audit logs the events of the mks service related to integration with Container Registry;
updated the Karpenter provider — Karpenter now correctly calculates the amount of memory available after the operating system has loaded and selects flavors with sufficient resources to run pods;
added the cni_type parameter to the selectel_mks_cluster_v1 resource — the network plugin (CNI) type can now be selected when creating a cluster via Terraform.

February

added to audit logs the events of the mks service;
removed the network card limitation in clusters on dedicated servers — it is now possible to use network cards with 10 Gbps and 25 Gbps connection speeds;
added support for ephemeralStorage during autoscaling with Cluster Autoscaler and Karpenter;
added the option to view in the Control Panel the user data that you specified when creating a cluster on a cloud server or adding a new node group;
added the pigz utility to the worker node image, which speeds up container image unpacking due to multi-threaded layer processing. The containerd container runtime automatically starts using the pigz utility. No additional configuration is required.

January

updated the autoscaling process using Karpenter:
- sped up the scaling process by creating multiple NodeClaims in parallel;
- added UserData support in NodeClass;
- added PriorityClassName to the Karpenter installation Helm chart.

December

updated the list of Kubernetes versions: added version 1.34 and removed Kubernetes version 1.31.

The list of available versions can be found in the Versions section of the Managed Kubernetes product description;
added the option to create Managed Kubernetes clusters on dedicated servers with GPU;
added the option to specify a CIDR for the node group subnet in a Managed Kubernetes cluster on dedicated servers when creating a cluster and adding a node group;
added to the Control Panel on the cluster page information about the network plugin (CNI) you selected when creating the cluster.

November

preemptible node groups are now available in the St. Petersburg, Moscow, and Novosibirsk regions;
added to the delete cluster form a field for specifying the reason for cluster deletion.