Skip to main content

Release notes in Managed Kubernetes

2026

  • Modified the node group creation form in the control panel:
    • Removed the need to open a modal window to select configurations;
    • renamed configurations: custom configurations are now Standard, and fixed GPU configurations are now GPU.
  • 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 guide;

  • Moved Managed Kubernetes to a separate section of the control panel;

  • Added the ability to use a single StorageClass for multiple segments of the same pool. An example manifest can be found in the Persistent Volumes guide.

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

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

    • Pod Security Standards — defines allowed profiles at the cluster level;
    • OPA Gatekeeper and Kyverno policies — can require the application of specific profiles;
    • Runtime Security — for example, Security Profiles Operator, KubeArmor. For more information on restricting resource access using AppArmor, see the Restrict a Container's Access to Resources with AppArmor Kubernetes documentation.
  • 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 section of the Managed Kubernetes Product Description guide;

  • updated the containerd configuration storage format on worker nodes — configuration is now 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, such as 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 creating a cluster. For existing clusters, the changes will be applied automatically when worker nodes are reinstalled or when a new node group is created.

  • added mks service audit log events related to integration with Container Registry;
  • updated the Karpenter provider — Karpenter now correctly calculates the amount of memory available after the operating system boots and selects flavors whose resources are sufficient to run pods;
  • added the cni_type parameter 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 audit log events;
  • removed the network card restriction in clusters on dedicated servers — you can now use 10 Gbps and 25 Gbps network cards;
  • added ephemeralStorage support for autoscaling with 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 through multi-threaded layer processing. The containerd container runtime automatically starts using the pigz utility. No additional configuration or setup 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 installation Helm chart.

2025