Provisioning Block Volumes on Multiple VAST Clusters

VAST Block 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.

Note
Class-specific parameters take precedence over global parameters that apply to all classes.

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

Create 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 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 driver's Helm chart:
  - The namespace where the secret is created
  Note
  When provisioning storage on multiple VAST clusters for Kubernetes ephemeral volumes, the namespace where the Kubernetes secret is created must be the same as the namespace where the driver's Helm chart is installed.
Create a new storage 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 driver's Helm chart, specify the secret's namespace on the secretNamespace parameter.

If a storage class does not contain the secretName parameter, VAST Block CSI Driver uses the information from the secretName and endpoint parameters specified in the driver's Helm chart configuration file (values.yaml) for all storage classes.