Release 2.12.1 (2025 Q4)
- Kubernetes version: 1.34.1
- The release is supported. See release policy.
Available versions for transition
| Source version | Update notes |
|---|---|
| 2.11.0 | no, the update is seamless |
| 2.12.0 | no, the update is seamless |
What’s new
- Cleaning up OpenSearch resources and access rights in access sets when upgrading a cluster from 2.10 to 2.12.
- Added conditions for NodeConfig of the cluster node.
- Increased the memory limit of the Cilium operator for running the Cluster Network Management Module (shturval-networking) when updating the cluster.
Bugs fixed
- Creating a client cluster with the name of a previously deleted cluster.
- Displays a warning about unsaved changes without making edits in the GUI when navigating from the Node Group Configuration page.
- Display cached data in the GUI on the cluster dashboard when switching between clusters.
- Creating VM templates (with the stc utility) on Ubuntu 24.04 OS without first removing the time synchronization package (systemd-timesyncd, chrony).
- FQDN Ingress generation in ssc shturval-ingress-controller after updating the cluster for display in the GUI.
- Installation of a temporary (bootstrap) cluster using the shtil utility with Podman.
- Access for users with “cluster” level rights to configure alerting on the pages of the “Notification” section in the GUI.
- Restrictions for displaying minutes in the time range settings window on the “Logs” and “Metering” tabs of the cluster dashboard.
- Calls to the shturval repository when installing the platform in a closed environment.
- Installing the Service Container Image Scanning Module (shturval-scanner) in a cluster with the vSphere provider and the vSphere CSI Module (shturval-capvs-csi) installed.
- Output ClassIngress data when viewing ClusterIssuers in the GUI.
- Configurations of a group of Worker nodes in the GUI of the cluster with the vSphere provider when copying settings from the InfraMachineTemplate.
- It is mandatory to change the default drain parameters to launch it from the GUI.
- Creating a cluster with the Yandex Cloud provider without selecting a cluster profile in the GUI.
- Behavior when deleting a cluster with a vSphere provider from the GUI.