---
title: "Release notes in Managed Kubernetes"
sidebar_label: "Release notes"
sidebar_position: 99
description: "Updates in Managed Kubernetes"
---
import {FaqWrapper, FaqItem, FaqQuestion, FaqAnswer} from 'docs-kit/components'
import Formbricks from '@theme/MDXComponents/Formbricks'
# Release notes in Managed Kubernetes
## 2026 \{#2026}
August
* updated the list of supported Kubernetes versions: added version 1.36 and removed version 1.33.
A list of supported versions is available in the [Versions](/managed-kubernetes/about/about-managed-kubernetes.mdx#versions) subsection of the [Managed Kubernetes Product Description](/managed-kubernetes/about/about-managed-kubernetes.mdx);
* moved Managed Kubernetes to a separate section in the Control panel.
July
* added support for two types of kernel modules in pre-installed drivers for GPU node groups. The kernel module type depends on the GPU architecture and is selected automatically. More details in the [Drivers for GPU Node Groups in a Managed Kubernetes Cluster](/managed-kubernetes/node-groups/gpu-drivers.mdx) guide;
* added AppArmor packages to the worker node image. AppArmor is a Linux kernel security module that restricts process access to worker node resources using profiles. AppArmor is used with:
* with Pod Security Standards — define acceptable profiles at the cluster level;
* with OPA Gatekeeper and Kyverno policies — can require the use of specific profiles;
* Runtime Security — for example, Security Profiles Operator, KubeArmor. More details on restricting access to resources using AppArmor in the [Restrict a Container's Access to Resources with AppArmor](https://kubernetes.io/docs/tutorials/security/apparmor/) guide in the Kubernetes documentation.
June
* added user data support in clusters on dedicated servers. More details about user data in the [User Data in Managed Kubernetes Node Groups](/managed-kubernetes/node-groups/user-data.mdx) guide;
* updated the list of applications that can be installed in a Managed Kubernetes cluster via the Control panel — added the ability to [install the Envoy Gateway application](/managed-kubernetes/clusters/applications.mdx#install-envoy-gateway) and removed the option to install the NGINX Ingress Controller application;
* changed the link to Managed Kubernetes in the Control panel. The new link is https://my.selectel.ru/mks/.
May
* added a new cluster type — a fault-tolerant multi-zone cluster. Available only in the [multi-zone pool](/infrastructure/locations.mdx#multi-az-pool) ru-6. More details about cluster types in the [Cluster Types](/managed-kubernetes/about/about-managed-kubernetes.mdx#cluster-types) subsection of the [Managed Kubernetes Product Description](/managed-kubernetes/about/about-managed-kubernetes.mdx);
* added [mks service](/audit-logs/events.mdx#managed-kubernetes) events related to the Envoy Gateway application to audit logs.
April
* updated the list of supported Kubernetes versions: added version 1.35 and removed version 1.32.
A list of supported versions is available in the [Versions](/managed-kubernetes/about/about-managed-kubernetes.mdx#versions) subsection of the [Managed Kubernetes Product Description](/managed-kubernetes/about/about-managed-kubernetes.mdx);
* 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 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. More details on configuring containerd registries via the `hosts.toml` file in the [containerd documentation](https://github.com/containerd/containerd/blob/main/docs/hosts.md) 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, changes will be applied automatically when worker nodes are reinstalled or when a new node group is created.
March
* added [mks service](/audit-logs/events.mdx#managed-kubernetes) events related to integration with [Container Registry](/craas/);
* 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 start pods;
* added the `cni_type` parameter to the [selectel\_mks\_cluster\_v1](https://registry.terraform.io/providers/selectel/selectel/latest/docs/resources/mks_cluster_v1) resource — you can now select the network plugin (CNI) type when creating a cluster via Terraform.
February
* added [mks service](/audit-logs/events.mdx#managed-kubernetes) events to audit logs;
* removed the restriction on network cards in clusters on dedicated servers — you can now use network cards with a connection speed of 10 Gbps and 25 Gbps;
* added support for ephemeralStorage when [autoscaling with Cluster Autoscaler](/managed-kubernetes/node-groups/autoscaling.mdx#autoscaling-with-cluster-autoscaler) and [Karpenter](/managed-kubernetes/node-groups/autoscaling.mdx#autoscaling-with-karpenter);
* added the ability to view [user data](/managed-kubernetes/node-groups/user-data.mdx) in the Control panel, which you specified when [creating a cluster on a cloud server](/managed-kubernetes/create/create-cloud-cluster.mdx) or [adding a new node group](/managed-kubernetes/node-groups/create-node-group.mdx);
* added the `pigz` utility to the worker node image, which speeds up the unpacking of container images through multi-threaded layer processing. The containerd container runtime automatically starts using the `pigz` utility. No additional setup or configuration is required.
January
* updated the autoscaling process with Karpenter:
* accelerated the scaling process by creating multiple NodeClaims in parallel;
* added UserData support in NodeClass;
* added PriorityClassName to the Karpenter installation Helm chart.
## 2025 \{#2025}
December
* updated the list of supported Kubernetes versions: added version 1.34 and removed Kubernetes version 1.31.
A list of supported versions is available in the [Versions](/managed-kubernetes/about/about-managed-kubernetes.mdx#versions) subsection of the [Managed Kubernetes Product Description](/managed-kubernetes/about/about-managed-kubernetes.mdx);
* added the ability to [create Managed Kubernetes clusters on dedicated servers with GPU](/managed-kubernetes/create/create-dedicated-gpu-cluster.mdx);
* added the ability to specify a CIDR for a node group subnet in a Managed Kubernetes cluster on dedicated servers when [creating a cluster](/managed-kubernetes/create/create-dedicated-cluster.mdx) and [adding a node group](/managed-kubernetes/node-groups/create-node-group.mdx#add-node-group-with-dedicated-nodes);
* added information about the network plugin (CNI) you selected when [creating the cluster](https://my.selectel.ru/mks/) to the cluster page in the Control panel, which you selected when [creating the cluster](/managed-kubernetes/create/).
November
* [preemptible node groups](/managed-kubernetes/node-groups/preemptible-node-groups.mdx) are now available in the regions of St. Petersburg, Moscow and Novosibirsk;
* added a field to the [cluster deletion](/managed-kubernetes/clusters/delete-cluster.mdx) form for specifying the reason for cluster deletion.