Release 2.13.1 (2026 Q1)

What’s new #

• Auto-generating annotation with key “cert-manager.io/common-name” added to Ingresses shturval-backend, shturval-frontend, sh-authn for correct ClusterIssuer Vault operation.
• Priorities set for system ShturvalServicePatch; warning annotation about modification prohibition added.
• ArgoCD version updated to 3.2.1.
• Certificate validation added when installing management cluster via command line flags with VK Cloud provider.
• Cluster and provider configuration checks added to YAML manifests for platform installation:
  • minimum CPU and memory resource values check;
  • Boolean value validation;
  • numeric value correctness check.

GUI #

Installed services management GUIs in cluster improved:

• system name — service instance name — output added;
• service card displays Patched status when ShturvalServicePatch applied;
• services with ShturvalServicePatch sorting available;
• ShturvalServiceConfig manifest tab added.

Bugs fixed #

When installing with shtil #

• Force configuration and resource update parameter application when installing cluster via command line flags with any infrastructure provider.
• Corporate certificate name annotation in monitoring Ingress (shturval-monitoring-vminsert) when installing cluster with self-signed certificate.
• Mandatory security check skip requirement when installing in closed environment with trusted certificate registry.

In the GUI #

• Namespace dashboard page crash under medium load.
• Node label management error due to conflict with auto-generated Ingress label.
• Automatic node scaling in groups ignored during cluster installation.
• Folder autocomplete in vSphere provider instance configuration.
• “Except selected namespaces” copy rule excluded when creating backup in cluster.
• Namespace custom access set without platform permissions not displayed on “Access Tree” page in platform.
• ServiceAccount GUI access error with cluster role binding.