Yandex Managed Service for Kubernetes release notes

Updates appear in the service's release channels in a sequence. First, updates with new features and improvements are released in the rapid channel, after a while, in the regular channel, and only then they become available in the stable channel.

Q4 2024Q4 2024

New featuresNew features

• Added support for Kubernetes version 1.31. For more information, see Release channels.
• Updated Cilium from version 1.12.9 to 1.15.10 for clusters with Kubernetes version 1.31 and higher.
• Updated CoreDNS from version 1.9.4 to 1.11.3 for all supported Kubernetes versions.

Fixes and improvementsFixes and improvements

• Added a preflight check for compatibility of objects or configurations with the new Kubernetes version before cluster upgrade.

  If the check identifies incompatible objects or configurations, the upgrade will return an error with a list of incompatible resources and a description.

  Currently, only Cilium network policies are checked.

• Fixed an issue that in some cases made it impossible to connect a new node to the cluster, the node ending up with a permanent NOT_CONNECTED status.

Q3 2024Q3 2024

New featuresNew features

Added support for migrating masters between subnets within a single availability zone.

Fixes and improvementsFixes and improvements

• Fixed the error that prevented saving cluster audit log files with records larger than 128 KB. Record clipping is now enabled.
• Revised the cluster roles for the Cilium network policy controller. Now they have only the minimum required permissions.
• Added subnet-id field validation when updating a node group using CLI, Terraform, and API. Now, if both the network-interface and locations parameters are specified in an update request, the subnet-id fields under locations must either be all empty or fully match the subnet-id list under network-interface (the subnet-id items may be listed in any order). If the network-interface array in your request has more than one element, the subnet-id fields under locations must be empty.

H1 2024H1 2024

New featuresNew features

• Added support for Kubernetes 1.28, 1.29, and 1.30. For more information, see Release channels.
• Updated CSI limits to support disks larger than 200 TB.

Fixes and improvementsFixes and improvements

• Fixed an error that could cause the snapshot size to be missing when PersistentVolume was large.
• Fixed an error where, during some node group updates, routes would fail to update to podCIDR, causing pods on the node to be unavailable.
• Fixed a number of vulnerabilities in runC.
• Fixed a problem with running a cluster after updating certificates while it was stopped.
• Fixed an error that, in some cases, caused a new node to permanently remain in the NOT_CONNECTED status.

20232023

Release 2023-6Release 2023-6

In the rapid, regular, and stable release channels, the following updates are available:

• Added support for ultra high-speed network storages with three replicas (SSD) for storage classes and persistent volumes.
• Node groups can now be used with GPUs without preinstalled drivers. Now you can use the GPU Operator application to select an appropriate driver version. For more information, see Using node groups with GPUs and no pre-installed drivers.
• Removed the CPU resource restriction imposed on CoreDNS pods to prevent throttling.
• Added support for placement groups of non-replicable disks in the Kubernetes CSI driver. Placement group parameters are available for storage classes.
• Fixed the error of ignoring a log group ID when updating the master_logging parameter in a cluster.
• Updated the Calico network controller to version 3.25 for Kubernetes versions beginning with 1.24.

Release 2023-5Release 2023-5

In the rapid, regular, and stable release channels, the following updates are available:

• Fixed the issue where the Guest Agent on nodes would access a resource outside a cluster.
• Updated the patch version for Kubernetes version 1.27.
• Added support for Kubernetes version 1.26.