Skip to main content

Release notes in Managed Kubernetes

2026

August
July
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 description guide;

  • updated the storage format for 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 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. For more details on configuring containerd registries via the hosts.toml file, see 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 the integration with Container Registry to audit logs;
  • 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 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.
February
  • added mks service events to audit logs;
  • removed the network card restriction in clusters on dedicated servers — you can now use network cards with connection speeds of 10 Gbps and 25 Gbps;
  • added support for ephemeralStorage when autoscaling with Cluster Autoscaler and Karpenter;
  • added the ability to view the user data you specified when creating a cluster on a cloud server or adding a new node group in the Control Panel;
  • added the pigz utility to the worker node image, which speeds up container image extraction due to 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 through parallel creation of multiple NodeClaims;
    • added UserData support in NodeClass;
    • added PriorityClassName to the Karpenter Helm chart.

2025

December
November