… VAST CSI Driver in a Kubernetes namespace other than default . Otherwise, skip to step 4. (Optional) Assign OpenShift SCCs to VAST CSI Driver. Note This step is required if you are going to deploy VAST CSI Driver in an OpenShift …

… StorageClassDefaults ). (Optional) Create a Kubernetes namespace for VAST CSI Driver. Note This step is required if you are going to deploy VAST CSI Driver in a Kubernetes namespace other than default . Otherwise, skip to step 4. Configure the VAST cluster …

… environment meets the requirements . Tip If you are going to deploy VAST CSI Driver in an OpenShift environment, consider using VAST CSI Operator to facilitate the deployment. See here for more information and guidelines. VAST CSI Driver is deployed using …

… cluster where the kubelet root directory is not /var/lib/kubelet . The following snippet shows a sample configuration file for VAST CSI Driver: secretName: "vast-mgmt" endpoint: "vms.example.com" deletionVipPool: "vippool-1" deletionViewPolicy: "default" verifySsl: true StorageClassDefaults: volumeNameFormat: "csi …

… is the name of the VAST CSI Driver Helm repository . is the name of the Helm chart to be installed ( vastcsi ). .yaml is the Helm chart configuration file for VAST CSI Driver. (optional) determines the Kubernetes namespace to which the …

… Policies . For more information about VAST Cluster QoS policies, see VAST Cluster Administrator's Guide . Extra Configuration Steps for Legacy CSI Local-Mount Deletions If you are going to use VAST CSI Driver with a VAST cluster where the Trash …

… cluster where the kubelet root directory is not /var/lib/kubelet . The following snippet shows a sample configuration file for VAST CSI Driver: secretName: "vast-mgmt" endpoint: "vms.example.com" deletionVipPool: "vippool-1" deletionViewPolicy: "default" verifySsl: true StorageClassDefaults: volumeNameFormat: "csi …

… CSI Driver's Helm chart, add this parameter to specify the namespace of the Kubernetes secret. (Optional) Configure registration of VAST CSI Driver with kubelet : kubeletPath: " " (optional): Add this option if you are going to run VAST CSI Driver on …

{font-size:1rem;} ul li p[data-block-id] {margin-bottom: 0;} ul[data-type="taskList"] li div p[data-block-id] {margin-bottom: 0;} ol li p[data-block-id] {margin-bottom: 0;} table tbody th p[data …

By default, VAST CSI Driver is deployed to the default namespace on the Kubernetes cluster. If you want to use a different Kubernetes namespace for VAST CSI Driver, create it prior to deployment by running the following command: kubectl create …

p[data-block-id]:empty::after {content: "\00A0";} p[data-block-id] {font-size:1rem;} ul li p[data-block-id] {margin-bottom: 0;} ul[data-type="taskList"] li div p[data-block-id] {margin-bottom: 0;} ol li p …

Create a Kubernetes secret to keep VMS user credentials or authentication token that VAST CSI Driver uses to communicate with the VAST cluster. You need to supply the name of the secret when creating the driver's Helm chart configuration …

… to the VAST CSI Driver repository when running Helm commands. For example: vastcsi Verify that the repository has been added: helm repo list The output is similar to the following: NAME URL vastcsi https://vast-data.github.io/vast-csi

… privileged -z -vast-node-sa -n Where: identifies the VAST CSI Driver release being deployed. is the namespace to which VAST CSI Driver will be deployed. For example: oc adm policy add-scc-to-user privileged -z csi-vast-controller …

Create a Kubernetes secret to keep VMS user credentials that VAST CSI Driver uses to communicate with the VAST cluster. You need to supply the name of the secret when creating the driver's Helm chart configuration file. The Kubernetes …

… snapshot.storage.k8s.io_volumesnapshots.yaml kubectl apply -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/v7.0.1/deploy/kubernetes/snapshot-controller/rbac-snapshot-controller.yaml kubectl apply -f https://raw.githubusercontent.com/kubernetes-csi/external-snapshotter/v7 …

CRDs for VAST snapshots are a prerequisite for using VAST snapshots. The CRDs are required if your deployment includes one or more snapshot classes. The driver's logic for creating snapshot classes varies depending on whether you specify the Kubernetes …

By default, VAST CSI Driver is deployed to the default namespace on the Kubernetes cluster. If you want to use a different Kubernetes namespace for VAST CSI Driver, create it prior to deployment by running the following command: kubectl create …

Create a Kubernetes secret to keep VMS user credentials that VAST CSI Driver uses to communicate with the VAST cluster. You need to supply the name of the secret when creating the driver's Helm chart configuration file. The Kubernetes …

… is the name of the VAST CSI Driver Helm repository . is the name of the Helm chart to be installed ( vastcsi ). .yaml is the Helm chart configuration file for VAST CSI Driver. (optional) determines the Kubernetes namespace to which the …