Skip to main content

Release notes in Managed Kubernetes

2026

August

  • 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 overview;

  • moved Managed Kubernetes to a separate section of the Control Panel;

  • added the ability to use one StorageClass for multiple segments of the same pool. An example manifest can be found in the Persistent Volumes instructions.

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. For more information, see the Drivers for GPU node groups in a Managed Kubernetes cluster instructions;

  • added AppArmor packages to the worker node image. AppArmor is a Linux kernel security module that restricts the access of processes to worker node resources using profiles. AppArmor is used with:

    • with Pod Security Standards — they define the allowable profiles at the cluster level;
    • with OPA Gatekeeper and Kyverno policies — they may require the application of certain profiles;
    • Runtime Security — for example, Security Profiles Operator, KubeArmor. For more information about restricting access to resources using AppArmor, see the Restrict a Container's Access to Resources with AppArmor guide in the Kubernetes documentation.
June
May
April

  • 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 overview;

  • updated the storage format of the containerd configuration on worker nodes — now the configuration is stored in the /etc/containerd/certs.d/docker.io/ directory in the hosts.toml file. This allows adding directories for custom registries and configuring them separately, for example, you can specify a CA certificate for self-signed TLS or disable 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 creating a cluster. In existing clusters, the changes will be applied automatically when re-installing worker nodes or creating a new node group.

March
  • added events of the mks service related to integration with Container Registry to audit logs;
  • updated the Karpenter provider — Karpenter now correctly calculates the amount of memory available after the operating system is loaded and selects flavors with sufficient resources to start pods;
  • added the cni_type parameter to the selectel_mks_cluster_v1 resource — now the network plugin (CNI) type can be selected when creating a cluster via Terraform.
February
  • added events of the mks service to audit logs;
  • removed the network card limitation for clusters on dedicated servers — you can now use network cards with connection speeds of 10 Gbps and 25 Gbps;
  • added support for ephemeralStorage during autoscaling using Cluster Autoscaler and Karpenter;
  • added the ability to view user data in the control panel 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 enabling 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 Helm chart for Karpenter installation.

2025

December
November