Release 2.13.1 (2026 Q1)

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

Available versions for transition #

¹ When upgrading from 2.11.x to 2.13.x, if logs are collected in the cluster, disable “Local log collection module (Vector)” (shturval-log-collector) before starting the update. Once the update is complete, re-enable this module. Logs collected before the upgrade and placed in the VLogs log storage component will remain available after the upgrade. If metrics are collected in the cluster, disable “Monitoring module control component (VictoriaMetrics Agent)” (shturval-metrics-collector) before starting the update. Once the update is complete, re-enable this module. Metrics collected before the upgrade and stored in the VictoriaMetrics metrics storage component will remain available after the upgrade.

² When updating, the application of system ShturvalServicePatch can be overridden by the values of custom values, which were changed directly in ShturvalServiceConfig services or set in ShturvalServicePatch. Before running the update, move such changes to ShturvalServicePatch and set a higher priority (to patchOrder, specify a value greater than 10000).

What’s new #

• In Ingresses shturval-backend, shturval-frontend, sh-authn, auto-generating annotation with the key “cert-manager.io/common-name” has been added for correct operation of ClusterIssuer Vault.
• For system ShturvalServicePatch, priorities have been set and an annotation has been added with a warning about prohibiting changes.
• Updated Argo CD version to 3.2.1.
• Added certificate validation when installing a cluster command line flag management cluster with the VK Cloud provider.
• For platform installation, cluster and provider configuration checks have been added in YAML manifests:
  • checking the minimum values for CPU resources and node memory;
  • validation of Boolean values;
  • checking the correctness of numerical values.

GUI #

The management GUIs for installed services in the cluster have been improved:

• added system name output - service instance name;
• the service card displays the Patched status if ShturvalServicePatch is applied to the service;
• sorting of services with ShturvalServicePatch applied is available;
• added a tab with the ShturvalServiceConfig manifest.

Bugs fixed #

When installing with shtil #

• Applying the option to force configuration and resource updates when installing cluster command line flags with any infrastructure provider.
• Installing an annotation with the name of a corporate certificate in Ingress monitoring (shturval-monitoring-vminsert) when installing a cluster with a self-signed certificate.
• Requirement to skip security checks when installing in a closed environment, when the registry has trusted certificates.

In the GUI #

• Namespace dashboard page crashes under medium load.
• Error in the ability to manage node labels due to a conflict with the auto-generated Ingress label.
• Ignoring the automatic scaling of nodes in groups when installing a cluster.
• Folder autocomplete in vSphere provider instance configuration.
• Exception to the established copying rule “except for selected namespaces” when creating a backup copy in a cluster.
• Lack of display of a native custom set of accesses without platform permissions on the “Access Tree” page in the platform.
• Error accessing the ServiceAccount interface associated with a cluster role.