Release 2.14.1 (2026 Q3)

• Kubernetes version: 1.35.1
• The release is supported. See release policy.

Available versions for transition #

Known limitations #

• Updating a cluster with the oVirt provider and the oVirt CSI module (shturval-capov-csi) enabled may stop at the SystemServicesUpdated stage with the SSCUpdateWait reason. The shturval-capov-csi service update fails because the spec.selector field of the shturval-capov-csi-node DaemonSet and the shturval-capov-csi-ovirtplugin Deployment is immutable (field is immutable), and the release rollback is not possible.

  To continue the update, stop the service management module (shturval-services), delete the CSI workloads, then start shturval-services again:

  1. Scale the shturval-services Deployment in the shturval-services-system namespace to 0 replicas:

  kubectl -n shturval-services-system scale deployment/shturval-services --replicas=0
  

  2. Delete the CSI Deployment and DaemonSet:

  kubectl --ignore-not-found=true -n shturval-capov-csi delete deployment/shturval-capov-csi-csi-ovirtplugin daemonset/shturval-capov-csi-node
  

  3. Scale the shturval-services Deployment to 1 replica:

  kubectl -n shturval-services-system scale deployment/shturval-services --replicas=1
  

  The controller recreates the CSI workloads, after which the system services update stage can complete.

Bugs fixed #

Update #

• Cyclic reboot of Control Plane nodes when updating a cluster initially deployed on version 2.10.0 or earlier with a self-signed or corporate certificate.
• Missing validation of the client ID in the Keycloak configuration when updating a management cluster with Keycloak connected.
• Update of a management cluster with a single Control Plane node hanging while updating the shturval-auth service.
• Configuration apply error when updating a cluster with Ubuntu 24.04 (Noble).
• Configuration apply error when updating a cluster with ALT Server 10.4 (Mendelevium) due to installed package drift.
• Error applying kernel parameters when creating VM templates on RHEL 9, Rocky Linux 9, and SberLinux.
• Handling of old Ingress configurations when updating the management cluster: the platform correctly detects the legacy Ingress scheme and applies a compatible update scenario.
• Removed the need to delete free hosts of the Shturval v2 provider before updating the cluster.

Operations and providers #

• Client cluster deployment error with the VMware vCloud Director provider after the Control Plane nodes have been brought up.
• Ignoring the selected VM template in InfraMachineTemplate when adding or editing Worker node groups in clusters with the VMware vSphere provider.
• Use of the default StorageClass when CSI is enabled in clusters with the VMware vCloud Director provider.
• Cluster deployment error with the oVirt provider when installing with flags.
• Added warnings and preliminary checks for installation with rootless Podman.
• Added diagnostics for VM template preparation errors when GRUB configuration generation exceeds the timeout.

GUI #

• The cluster configuration validation message text has been clarified.
• Fixed display of access application statuses for in-cluster tenants.