Remove VAST CSI Driver 2.1.x or 2.0.x

Prev Next

After removal of VAST CSI Driver 2.1.x or 2.0.x, the existing containers will continue to run with the volumes provisioned by the removed VAST CSI Driver.

  1. Remove all VAST storage classes:

    kubectl delete sc vastdata-filesystem
  2. Remove the VAST CSI driver:

    kubectl delete csidriver csi.vastdata.com
  3. Remove the VAST namespace:

    kubectl delete all --all -n vast-csi
  4. Remove the VAST ServiceAccounts:

    kubectl delete sa csi-vast-controller-sa -n vast-csi
    kubectl delete sa csi-vast-node-sa -n vast-csi
  5. Remove the VAST Secret:

    kubectl delete secret csi-vast-mgmt -n vast-csi
  6. Remove the VAST ClusterRole:

    kubectl delete ClusterRole csi-vast-attacher-role
    kubectl delete ClusterRole csi-vast-provisioner-role
  7. Remove the VAST ClusterRoleBinding:

    kubectl delete ClusterRoleBinding csi-resizer-role
    kubectl delete ClusterRoleBinding csi-vast-attacher-binding
    kubectl delete ClusterRoleBinding csi-vast-provisioner-binding
  8. Remove the VAST VolumeSnapshotClass:

    kubectl delete VolumeSnapshotClass vastdata-snapshot