VAST CSI Driver 2.7.1 has been released in October 2026. This release includes:
Enhancements
- VCSI-679: Added an ability to set the NFS protocol version that the driver uses when handling deletions on a VAST cluster with Trash Folder Access disabled. To do so, specify the
deletionMountOptionsoption in the storage class definition (together withdeletionVipPoolanddeletionViewPolicy). For example:- To use NFSv3:
deletionViewPolicy:
deletionVipPool:
deletionMountOptions: vers=3 - To use NFSv4:
deletionViewPolicy:
deletionVipPool:
deletionMountOptions: "vers=4.2,proto=tcp"
If thedeletionMountOptionsoption is not specified, the driver uses NFSv3 for legacy local-mount deletions.
- To use NFSv3:
- Operator:
kube-rbac-proxy sidecarmoved fromdocker.io/kubebuilder/kube-rbac-proxytoquay.io/brancz/kube-rbac-proxy(digest-pinned). Air-gap must mirror the new image. - VastExtensions gRPC requires TLS on TCP and Unix. Charts generate a self-signed serving certificate and reuse it on upgrade.
- Extensions manager image ships the
vcsiCLI at/usr/local/bin/vcsi.
Resolved Issues
- VCSI-676: Resolved an issue that could cause an upgrade from 2.6.5-HF6, 2.6.5-HF7, 2.6.5-HF8 to 2.7.0 to fail due to volume name format discrepancy in manually created storage classes.
- VCSI-662: Eliminated a potential VAST CSI conroller memory leak that could occur when running with
verifySsl=falsein the driver's Helm chart.