--- title: "VAST CSI Driver 2.5.1 Release Notes" slug: "vast-csi-driver-251-release-notes-2-5" updated: 2026-11-06T00:21:24Z published: 2026-11-06T00:21:24Z canonical: "docs.vastdata.com/vast-csi-driver-251-release-notes-2-5" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.vastdata.com/llms.txt > Use this file to discover all available pages before exploring further. # VAST CSI Driver 2.5.1 Release Notes VAST CSI Driver 2.5.1 has been released to General Availability as of May 2025. To upgrade to VAST CSI/COSI Driver 2.5.0, follow the [upgrade](/develop/docs/upgrading-vast-csi-driver-2-5) procedure in the *VAST CSI Driver 2.5 Administrator's Guide*. **Note**: This driver version is not compatible with VAST Cluster 5.5.0 or later. ## 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](/develop/docs/create-a-helm-chart-configuration-file-for-vast-csi-driver-2-5). 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*](/develop/docs/running-multiple-instances-of-vast-csi-driver-2-5). ### 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] > **Note** > > Supplying `qos_policy_id` in the Helm chart configuration file (`values.yaml`) is not supported.