---
title: "VAST CSI Driver 2.6.3 Release Notes"
slug: "vast-csi-driver-263-release-notes-2-6"
description: "Upgrade to VAST CSI Driver 2.6.3 for enhanced OpenShift support, tenant-specific provisioning, and improved snapshot operations."
updated: 2026-11-03T22:44:01Z
published: 2026-11-03T22:44:01Z
canonical: "docs.vastdata.com/vast-csi-driver-263-release-notes-2-6"
---

> ## 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.6.3 Release Notes

VAST CSI Driver 2.6.3 was released to General Availability in August 2025.

To upgrade to VAST CSI Driver 2.6.3, follow the upgrade procedure in the [*VAST CSI Driver 2.6 Administrator's Guide*](/develop/docs/csi-driver-administrators-guide-2-6).

**Note**: This driver version is not compatible with VAST Cluster 5.5.0 or later.

## New Features and Capabilities

### Support of Two Driver Types in VAST CSI Operator for OpenShift

Starting with VAST CSI 2.6.3, VAST CSI Operator for OpenShift can be used to deploy both VAST CSI Driver (for NFS volumes) and VAST Block CSI Driver (for block volumes).

When creating the `VastCSIDriver` CRDs used to deploy the drivers on OpenShift using VAST CSI Operator, you need to specify the type of the driver you want to deploy using the new `driverType` parameter:

```plaintext
spec:
  driverType: "nfs"
```

or

```plaintext
spec:
  driverType: "block"
```

For more information, see [*VAST CSI Driver 2.6 Administrator's Guide*](/develop/docs/csi-driver-administrators-guide-2-6).

### Connection to a Specific VAST Cluster Tenant

When using VAST CSI Driver with VAST Cluster 5.3.3 or later, you can set up storage provisioning using a particular VAST cluster tenant.

To do so, in the [Kubernetes secret](/develop/docs/deploy-vast-csi-driver-2-6#create-kubernetes-secret-for-vast-csi-driver) that supplies the credentials to connect to the VAST cluster:

- Specify the desired tenant on the new `tenant` parameter.
- Use credentials of a VMS user that is the *Tenant Admin* for the tenant.

> [!NOTE]
> **Note**
> 
> VAST Cluster versions prior to 5.3.3 or do not allow using the *Tenant Admin* user type for VAST CSI.

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

### Waiting for Completion of VAST Snapshot and Clone Operations

VAST Block CSI Driver provides a new storage class parameter, `blockingClones`, that determines whether the driver should wait for VAST snapshot or clone operations to complete before the PVC can be attached to a pod. This ensures that the volume is fully usable and consistent at the time of provisioning, but may add a significant latency.

By default, the driver does not wait for completion of snapshot or clone operations before provisioning a PVC.

### VAST CSI Operator for Kubernetes

VAST CSI Driver can be deployed using [VAST CSI Operator for Kubernetes](/develop/docs/deploy-vast-csi-driver-2-6#deploy-vast-csi-driver-with-vast-csi-operator-for-kubernetes).