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.

    A list of supported versions is available in the Versions subsection of the Managed Kubernetes Product Description;

  • 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 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 guide in the Kubernetes documentation.
June
May
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 subsection of the Managed Kubernetes Product Description;

  • 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 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 events 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 start pods;
  • added the cni_type parameter to the selectel_mks_cluster_v1 resource — you can now select the network plugin (CNI) type when creating a cluster via Terraform.
February
  • added mks service 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 and Karpenter;
  • added the ability to view user data in the Control panel, which 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 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

December
November