Release 2.9.1 (2025 Q1)

• Kubernetes version: 1.31.3 – 1.31.8
• This release is no longer supported. See release policy.

Available versions for transition #

¹ When upgrading from 2.8.x to 2.9.x, follow the manual steps:

• Before starting the update, switch the “Local Log Collection Module” service (shturval-log-operator) to the Off (absent) mode and wait for the Uninstall state; then put it into On (auto) mode and wait for the Install, Sync state; after that, switch the service back to Off (absent) mode and wait for the Uninstall state.
• Before starting the update, switch the “Local Metrics Collection Module” service (shturval-metrics) to the Off (absent) mode and wait for the Uninstall state.
• After the update, transfer the user customizations for sending logs to the shturval-log-collector configuration.
• After the update, move the customizations for sending metrics from ShturvalServiceConfig shturval-metrics to ShturvalServiceConfig shturval-metrics-collector: rename alertmanager.alertmanagerSpec to alertmanager.spec, and move prometheus.prometheusSpec.remoteWrite to external.vm.write.
• After updating the management cluster, change the custom resource vmalert-<monitoringID> in the namespace of each cluster: in spec.notifiers set the existing element url to the value http://vmalertmanager-shturval-metrics-collector.victoria-metrics:9093.

Interface changes #

• During the cluster creation process, at the Master node configuration step, a role display in Read Only mode has been added.
• The viewing area for displaying the number of security events over the last hour by cluster has been increased.
• Added the ability to specify the repository address with login and password in the settings of the “Package Repositories” section in NCI.

Bug fixes #

• Behaviors when scaling Worker nodes of the management cluster in the GUI.
• Installation of several cluster nodes with the Shturval v2 provider on one VM.
• Installing services when rolling out a cluster.
• Automatic activation of the Vector local log collection module (shturval-log-collector) and the Victoria Metrics Agent monitoring module management component (shturval-metrics-collector) when updating the cluster from 2.8.1 to 2.9.1.
• A warning appears about unsaved changes without making changes when navigating from the “Routes” page.
• The “Try again” button works on GUI pages.
• Reduced pop-up notifications about unsaved changes in cluster Loads.
• Downloading cluster kubeconfig from the GUI.
• Navigation through menu sections in case of a page loading error in the GUI.
• Removing ConfigMap and Secret in the GUI after making changes to ConfigMap/Secret.
• Validation of specified labels on the page for adding notification blocking in the GUI.
• Mandatory indication of the namespace field when creating a network policy in the GUI.
• Connections when viewing logs in the “View container logs” window in the GUI.
• Displaying potentially available hosts at the “Configuration of Worker Nodes” step when initializing the creation of a cluster with the Shturval v2 provider.
• Editing the name of the default group of nodes (default) and its role at the “Configuration of Worker nodes” step when initializing the creation of a cluster.
• Descriptions in the error message when creating a VM (OVirtMachine).
• Gaining access to dashboards in Grafana after changing the authentication service from internal to external service (Keycloak).