Be sure to meet these requirements when configuring data protection in VMware Tanzu Mission Control.

  • Your cluster must be Kubernetes version 1.20 or greater.
  • Your cluster must be running a CSI driver capable of supporting volume snapshots at the v1 API level.
  • Your cluster must be installed with the API group.,, and CRDs should be present on the cluster. You should see output similar to that below:
    kubectl api-resources -o name | grep ""
    In addition to the CRDs, there is the expectation that the volume snapshot controller and the CSI snapshot sidecar container have also been installed. Read more about them in the Kubernetes documentation at external_snapshotter. These are typically installed by your cluster provider along with the above CRDs.
  • For every unique CSI provisioner in the cluster, there should be a matching volume snapshot class to exist, with a label ( Here is an example manifest:
    kind: VolumeSnapshotClass
      name: csi-azuredisk-vsc
      labels: "true"
    deletionPolicy: Delete

    The name of the driver must correspond to that specified in the persistent volume or the persistent volume’s storage class.

    kubectl get pv pvc-8835819c-4946-4b7d-8b13-58f827adb5ff -o jsonpath='{.spec.csi.driver}' 
    kubectl get storageclass managed -o jsonpath='{.provisioner}'
  • When restoring CSI volume snapshots across clusters, the name of the CSI driver in the destination cluster must be the same as that on the source cluster to ensure cross cluster portability of CSI volume snapshots. Additionally, the target cluster must have appropriate permissions to access the snapshots in the source cluster.