---
title: "Provisioning Volumes on Multiple VAST Clusters"
slug: "provisioning-volumes-on-multiple-vast-clusters-2-4"
updated: 2026-11-06T00:07:45Z
published: 2026-11-06T00:07:45Z
canonical: "docs.vastdata.com/provisioning-volumes-on-multiple-vast-clusters-2-4"
---

> ## 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.

# Provisioning Volumes on Multiple VAST Clusters

VAST CSI Driver enables you to provision volumes on multiple VAST clusters.

The VAST cluster to use can be specified per storage class, together with the user credentials needed to connect to the VAST cluster. You can also configure multiple storage classes to connect to the same VAST cluster using different user credentials.

If your Kubernetes volumes are protected with VAST Cluster snapshots, you can specify the VAST cluster and user credentials per snapshot class.

> [!NOTE]
> **Note**
> 
> Class-specific parameters take precedence over global parameters that apply to all classes.

To configure a storage class or a snapshot class to use a particular combination of a VAST cluster and user credentials:

1. [Create](/develop/docs/create-a-kubernetes-secret-with-vms-user-credentials-for-vast-csi-driver-2-4) a Kubernetes secret that will be used to provision storage on multiple VAST clusters. The secret specifies the following:

  - The hostname of the **VAST cluster** on which you want to provision volumes
  - The VMS user's **username** and **password**
  - If using [SSL encryption](/develop/docs/configuring-ssl-encryption-for-vast-csi-driver-2-4) with a self-signed SSL certificate:

    - The **SSL certificate** to be used to protect the connection
  - If you are creating the secret in a namespace that is different from the namespace used to install the VAST CSI Driver Helm chart:

    - The **namespace** where the secret is created

> [!NOTE]
> **Note**
> 
> When provisioning storage on multiple VAST clusters for Kubernetes [ephemeral volumes](/develop/docs/provisioning-ephemeral-volumes-2-4), the namespace where the Kubernetes secret is created must be the same as the namespace where the VAST CSI Driver Helm chart is installed.
2. [Create](/develop/docs/using-storage-classes-2-4#adding-a-storage-class) a new storage class (or a snapshot class) and supply the newly created secret using the `secretName` parameter of the class.

If you have creating the secret in a namespace that is different from the namespace used to install the VAST CSI Driver Helm chart, specify the secret's namespace on the `secretNamespace` parameter.

For example:

```plaintext
storageClasses:
  vastdata-filesystem1:
    storagePath: /foo
    viewPolicy: default1
    vipPool: vippool1
    secretName: vast-mgmt1
    secretNamespace: default
```

If a storage class or a snapshot class does not contain the `secretName` parameter, VAST CSI Driver uses the information from the `secretName` and `endpoint` parameters specified in the VAST CSI Driver [Helm chart configuration file](/develop/docs/create-a-helm-chart-configuration-file-for-vast-csi-driver-2-4) (`values.yaml`) for all storage classes.