Skip to main content

Release notes in Managed Kubernetes

2026

October
September
  • Updated the node group creation form in the control panel:
    • removed the need to open a modal window to select configurations;
    • renamed configurations. Custom configurations – to Standard, and fixed configurations with GPU – to GPU.
August

  • updated the list of supported Kubernetes versions: added version 1.36 and removed version 1.33.

    The list of supported versions can be found in the Versions section of the Managed Kubernetes product overview instructions;

  • 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. You can see a manifest example in the Persistent volumes instructions.

July

  • added support for two types of kernel modules in pre-installed drivers for node groups with GPU. The kernel module type depends on the GPU architecture and is selected automatically. Learn more in the Drivers for node groups with GPU in a Managed Kubernetes cluster instructions;

  • 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 Pod Security Standards — they define allowed profiles at the cluster level;
    • by OPA Gatekeeper and Kyverno policies — they can require the use of specific profiles;
    • in Runtime Security — for example, Security Profiles Operator, KubeArmor. Learn more about restricting access to resources with 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.

    The list of supported versions can be found in the Versions section of the Managed Kubernetes product overview instructions;

  • updated the storage format of the containerd configuration on worker nodes — the 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, 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 reinstalling worker nodes or creating a new node group.

March
  • added mks service events related to integration with Container Registry to audit logs;
  • updated the Karpenter provider — Karpenter now correctly calculates the amount of memory available after operating system boot and selects flavors whose resources are sufficient to run 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 mks service events to audit logs;
  • lifted the network card restriction in clusters on dedicated servers — you can now use network cards with a connection speed of 10 Gbps and 25 Gbps;
  • added ephemeralStorage support when 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 unpacking container images through multithreaded layer processing. The containerd container runtime automatically starts using the pigz utility. No additional enabling or configuration is required.
January

  • updated the autoscaling process using Karpenter:

    • accelerated the scaling process through parallel creation of multiple NodeClaims;
    • added UserData support in NodeClass;
    • added PriorityClassName to the Helm chart for installing Karpenter.

2025

December
November