Release notes in Managed Kubernetes
2026
-
updated the list of supported Kubernetes versions: added version 1.36 and removed version 1.33.
You can view the list of supported versions in the Versions subsection of the Managed Kubernetes product description guide.
- added information about the kernel modules used in pre-installed drivers for GPU node groups. For more details, see the Drivers for GPU node groups in a Managed Kubernetes cluster guide.
- added user data support in clusters on dedicated servers. For more details on user data, see the User data in Managed Kubernetes node groups guide;
- 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.
- added a new cluster type: a fault-tolerant multi-zone cluster. Available only in the multi-zone pool ru-6. For more details on cluster types, see the Cluster types subsection of the Managed Kubernetes product description guide;
- added mks service events related to the Envoy Gateway application to audit logs.
-
updated the list of supported Kubernetes versions: added version 1.35 and removed version 1.32.
You can view the list of supported versions in the Versions subsection of the Managed Kubernetes product description guide;
-
updated the storage format for containerd configuration on worker nodes — the configuration is now stored in the
/etc/containerd/certs.d/docker.io/directory in thehosts.tomlfile. This allows you to add directories for custom registries and configure them separately, for example, you can specify a CA certificate for a self-signed TLS or disable certificate verification. For more details on configuring containerd registries via thehosts.tomlfile, see 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 creating a cluster. In existing clusters, the changes will be applied automatically when reinstalling worker nodes or creating a new node group.
- added mks service events related to the integration with Container Registry to audit logs;
- 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_typeparameter to the selectel_mks_cluster_v1 resource — you can now select the Container Network Interface (CNI) type when creating a cluster via Terraform.
- added mks service events to audit logs;
- removed the network card restriction in clusters on dedicated servers — you can now use network cards with connection speeds of 10 Gbps and 25 Gbps;
- added support for ephemeralStorage when autoscaling with Cluster Autoscaler and Karpenter;
- added the ability to view the user data you specified when creating a cluster on a cloud server or adding a new node group in the Control Panel;
- added the
pigzutility to the worker node image, which speeds up container image extraction due to multi-threaded layer processing. The containerd container runtime automatically starts using thepigzutility. No additional setup or configuration is required.
-
updated the autoscaling process with Karpenter:
- accelerated the scaling process through parallel creation of multiple NodeClaims;
- added UserData support in NodeClass;
- added PriorityClassName to the Karpenter Helm chart.
2025
-
updated the list of supported Kubernetes versions: added version 1.34 and removed version 1.31.
You can view the list of supported versions in the Versions subsection of the Managed Kubernetes product description guide;
-
added the ability to create Managed Kubernetes clusters on dedicated servers with GPU;
-
added the ability to specify a CIDR for a node group subnet in a Managed Kubernetes cluster on dedicated servers when creating a cluster and adding a node group;
-
added information about the Container Network Interface (CNI) selected when creating a cluster to the cluster page in the Control Panel.
- preemptible node groups are now available in the regions of St. Petersburg, Moscow, and Novosibirsk;
- added a field to specify the reason for cluster deletion to the cluster deletion form.