VAST CSI Driver 2.6.5 is released to General Availability as of February 2026.
To upgrade to VAST CSI Driver 2.6.5, follow the upgrade procedure in the VAST CSI Driver 2.6 Administrator's Guide.
New Features
Export of Driver Metrics to Prometheus
VAST CSI Driver can be configured to expose CSI node and controller metrics in Prometheus format. The metrics include total counts and average durations for CSI RPCs, mounts/umounts, and also NFS transport (xprt) statistics. For more information and guidelines, see VAST CSI Driver Administrator's Guide.
Enhancements
VCSI-367: Added support for resolution of symlinks in kubelet mount paths (for example,
/dev/disk/by-uuid/*) when querying mount information. By default, the resolution is not performed. To enable it, add the new resolveMountSymlinks option to the driver's Helm chart configuration file.NOTE: The new option affects handling of symlinks by the driver. If you are using symlinks as device names, for example, you need to add
resolveMountSymlinks the new option to your Helm's chart configuration file.VCSI-343: Added an ability to determine how much time the driver waits for completion of a mount or umount command before terminating the attempt and returning an error. To set the timeout, use the new
mountUmountTimeout parameter in the driver's Helm chart configuration file. If the timeout is not set, the driver waits indefinitely. The default value is 30 seconds.VCSI-343: Enhanced driver logging to include detailed information about mount and umount operations.
Provided a new option named
disableUsageStats (in the driver’s Helm configuration file) to control whether the driver sends its usage statistics to the VAST cluster.
Resolved Issues
VCSI-345: Resolved an issue that could cause occasional
VolumeResizeFailed <...> kubelet NodeExpandVolume.NodeExpandVolume failed for volume <...> : Expander.NodeExpand found CSI plugin kubernetes.io/csi/csi.vastdata.com to not support node expansion errors when resizing volumes.