CSI Snapshot Feature Shows “Not Ready” Status for Cluster

Products

• VMware Tanzu Mission Control

Issue/Introduction

The CSI snapshot feature is enabled but remains in a “Not Ready” state for the cluster.

Environment

VMware Tanzu Mission Control

Cause

The snapshot feature requires manual installation of the necessary Custom Resource Definitions (CRDs) and the snapshot controller. The following components are likely missing:

1. Running the command kubectl get volumesnapshotclass returns an error stating that the server does not have a resource type “volumesnapshotclass”.
2. Checking for CRDs related to snapshots using kubectl get crds | grep volumesnapshot should output the following if the snapshot components are installed:
   • volumesnapshotclasses.snapshot.storage.k8s.io
   • volumesnapshotcontents.snapshot.storage.k8s.io
   • volumesnapshots.snapshot.storage.k8s.io
3. Verifying if the snapshot controller is running using kubectl get pods -n kube-system | grep snapshot. If the output is empty, the snapshot controller is not installed.

Resolution

1. Install the Kubernetes Volume Snapshot API components using the provided script. Refer to Volume Snapshot and Restore for installation steps.
   • Volume Snapshot and Restore
2. Ensure a VolumeSnapshotClass is created and correctly configured. Refer to Volume Snapshot and Restore for configuration details.
   • Volume Snapshot and Restore
3. Confirm compatibility of the CSI driver and vSphere version. The minimum requirements are:
   • vSphere 7.0 P03+
   • CSI 2.5.0+
4. Recheck that snapshots are recognized in Tanzu Mission Control (TMC) by running kubectl get volumesnapshotclass.
5. Test a backup to ensure the snapshot feature is functioning as expected.

Additional Information

Requirements for CSI Volume Backup