Release 2.11.0 (2025 Q3)

• Kubernetes version: 1.33.1
• This release is no longer supported. See release policy.

Available versions for transition #

¹ When upgrading from 2.10.x to 2.11.0, take into account the changes in storing logs and updating client clusters:

• The OpenSearch centralized log storage component is being replaced with VLogs. If OpenSearch was installed on a management cluster, the upgrade will remove the service and replace it with VLogs.
• Logs collected before the update and placed in the built-in OpenSearch centralized log storage component will be deleted.
• After updating the management cluster to 2.11.0, update all client clusters of the “Shturval” platform to a version no lower than 2.10.0.
• After updating the management cluster to 2.11.0, SSO in Argo CD will no longer work in client clusters with versions lower than 2.11.0.

What’s new #

Infrastructure #

• Added shtil-based GUI installer for the management cluster.
• The centralized log storage module (OpenSearch) has been replaced by storing cluster logs in VLogs instances in the management cluster.
• Added OS support: Rosa Chrome, Alt Linux 10, SberLinux 5.9.1, Rocky Linux 9, RED OS (6.12 kernel support), RHEL 9, Oracle Enterprise Linux 8.7
• Changed ingress (only for new installations): instead of back, front, auth there is now a single one - shturval.
• Added Auth-Operator system component.
• Added dashboards to Grafana for: Trivy vulnerabilities reports, Kyverno, Vector, VLogs, Cluster API.
• Removed dashboard in Grafana: Kube Proxy.
• VMware vCloud Director infrastructure provider.
• Increased catalog response time when authenticating users.
• The storage of platform administrator data has been changed: the data is moved to a custom resource, the password is stored in bcrypt hash format.

GUI: #

• Ability to install corporate, intermediate or ACME certificates when deploying client clusters
• Ability to specify an external balancer for the Kube API when deploying a client cluster with the Shturval v2 provider.
• Format for selecting system services when creating client clusters.
• Mandatory indication of the platform version when deploying client clusters.
• Ability to create a provider, deploy clusters and manage communication between nodes and the VMware vCloud Director provider.
• The namespace dashboard has been redesigned: it now provides operational information about workloads, their status, the presence of security threats, and resource consumption.
• Displaying network policies on the namespace dashboard.
• Displaying system logs on cluster dashboards.
• Displaying the availability of key system components on cluster dashboards.
• Ability to configure self-signed, corporate and intermediate certificates in Issuers, ClusterIssuers.
• Pod interface: added QoS display, terminal and log interface moved to tabs. Added logic for specifying Security Context depending on the Privileged attribute.
• Added display of information about containers and restarts on pages with Pods lists.
• You can download the pod log both with filters and the full one.
• The order in which a new created namespace is displayed when selecting a namespace during the installation of a system service.
• Ability to edit backup storage.
• Auto-update of pages with lists of objects.
• Ability to delete objects from object manifest tabs.
• Display of ShturvalServicePatch objects, allowing you to roll out changes to custom values of system services.
• Displaying service status in namespaces.
• Ability to assign access rights to users and groups without searching the LDAP directory.
• Display the reason in case of unsuccessful assignment of access rights.
• The default minimum value has been set as the technological window for cluster update schedules.
• Improved parameters and logic of fields in integration with LDAP.

Fixed #

• Display the status of security policies in the GUI.
• Ability to specify user data when connecting a repository through a node configuration object
• Ability to assign access rights to groups containing CamelCase in the name.
• Error updating nodes with Shturval v2 provider.
• Validation so that the address of one of the cluster nodes cannot be specified as a VIP address.
• Shturval versions that are incompatible with the selected version of k8s have been excluded from the list of available ones when deploying client clusters.
• Units of measurement for resources when creating client clusters with the Yandex Cloud provider.

Known limitations #

• After upgrading the management cluster to 2.11.0, SSO in Argo CD will no longer work in client clusters with versions below 2.11.0.