Deploying VAST CSI Driver

Run the following Docker command to generate the YAML configuration file:

docker run -it --net=host -v `pwd`:/out vastdataorg/csi:v2.1.1 template

Where:

Respond to prompts as follows:

For example:

docker run -it --net=host -v `pwd`:/out vastdataorg/csi:v2.1.1 template

Unable to find image 'vastdataorg/csi:v2.1.1' locally
Trying to pull repository docker.io/vastdataorg/csi ...
v2.1.1: Pulling from docker.io/vastdataorg/csi
Digest: sha256:5dc0a5df9ffc2bc5b7cdfb4f59c47105457b8e6fba74a04045df1e6d5a94c207
Status: Downloaded newer image for docker.io/vastdataorg/csi:v2.1.1

Vast CSI Plugin - Deployment generator for Kubernetes

Name of this Docker Image: vastdataorg/csi:v2.1.1
Image Pull Policy (Never|Always|IfNotPresent|Auto): InNotPresent
Vast Management hostname: selab202.vastdata.com
Vast Management username: admin
Vast Management password: ******

Connected successfully! VMS Version: <version>
- VIP Pools: main
- Exports: /, /nfsshare

Virtual IP Pool Name: main
NFS Export Path: /k8s
Additional Mount Options:

Written to vast-csi-deployment.yaml

Inspect the file and then run:
>> kubectl apply -f vast-csi-deployment.yaml

Be sure to delete the file when done, as it contains Vast Management credentials

Run the following command:

kubectl apply -f vast-csi-deployment.yaml

When the command completes, run the following command and verify that you can see one csi-vast-controller-0 plus a csi-vast-node-xxxxx per worker node running. If they are shown as running, this means you have deployed VAST CSI Driver successfully.

kubectl get pods --all-namespaces -o wide

The output is similar to the following:

NAMESPACE   NAME                READY   STATUS    <...>
<...>
vast-csi    csi-vast-controller-0   3/3     Running   <...>
vast-csi    csi-vast-node-45mwc     2/2     Running   <...>
vast-csi    csi-vast-node-jhxm7     2/2     Running   <...>
vast-csi    csi-vast-node-kgq4b     2/2     Running   <...>
<...>

Delete the vast-csi-deployment.yaml file.

The generated YAML configuration file contains VAST Cluster credentials. Delete this file after the deployment procedure is complete. If necessary, you can regenerate it at any time.

Create a YAML configuration file with the following content:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: vast-pvc-1
spec:
  accessModes:
  - ReadWriteMany
  resources:
    requests:
      storage: 1Gi
  storageClassName: vastdata-filesystem

kind: StatefulSet
apiVersion: apps/v1
metadata:
  name: test-app-1
spec:
  serviceName: "test-service-1"
  replicas: 5
  selector:
    matchLabels:
      app: test-app-1
  template:
    metadata:
      labels:
        app: test-app-1
        role: test-app-2
    spec:
      containers:
        - name: my-frontend
          image: busybox
          volumeMounts:
          - mountPath: "/shared"
            name: my-shared-volume
          command: [ '/bin/sh', '-c', 'while true; do date -Iseconds >> /shared/$HOSTNAME; sleep 1; done' ]
      volumes:
        - name: my-shared-volume
          persistentVolumeClaim:
            claimName: vast-pvc-1

Apply the configuration:

kubectl apply -f <filename>.yaml

Monitor the VAST Cluster path specified in the root_export parameter in the YAML configuration file. You will see a PVC per container, in this example 5. In each, a date will be appended to a text file.