VAST CSI Driver 2.5.1 Release Notes

Prev Next

VAST CSI Driver 2.5.1 is released to General Availability as of May 2025.

To upgrade to VAST CSI/COSI Driver 2.5.0, follow the upgrade procedure in the  VAST CSI Driver 2.5 Administrator's Guide.

New Features and Capabilities

Running multiple instances of VAST CSI Driver

You can run multiple VAST CSI Driver instances on the same Kubernetes cluster.

To do so, deploy each instance under its own name specified on the csiDriverName parameter in the driver instance's Helm chart configuration file. Each driver instance needs to be deployed in its own namespace. After deployment, you can supply the driver instance name when specifying the provisioner for a storage class (or a snapshot class), as well as when supplying the driver name in your pod definition.Create a Helm Chart Configuration File for VAST CSI Driver

For more information, see the VAST CSI Driver 2.5 Administrator's Guide.

Passing VAST QoS policy ID for a Storage Class

In addition to specifying a QoS policy name for a storage class, you can also pass the ID of the QoS policy using the new qos_policy_id parameter in the storage class definition provided in a Kubernetes YAML configuration file.

Note

Supplying qos_policy_id in the Helm chart configuration file (values.yaml) is not supported.