How to fix MountVolume.SetUp failed: volume not found in Kubernetes

Verify the PVC exists and is bound:

kubectl get pvc -n <namespace>

Expected output shows Bound status:

NAME      STATUS   VOLUME    CAPACITY   ACCESS MODES   STORAGECLASS
my-pvc    Bound    pv-xxx    10Gi       RWO            standard

If status is Pending, the PVC hasn't found a matching PV.

View PersistentVolumes and their states:

kubectl get pv

Look for:
- Available: Can be bound to a PVC
- Bound: Attached to a PVC
- Released: PVC was deleted but PV retains data
- Failed: Reclamation failed

Check that the storage class referenced by the PVC exists:

# List storage classes
kubectl get storageclass

# Check PVC's requested storage class
kubectl get pvc <pvc-name> -o jsonpath='{.spec.storageClassName}'

If the storage class doesn't exist, create it or update the PVC.

If a PV is in Released state and you want to reuse it:

# Clear the claimRef to make PV available again
kubectl patch pv <pv-name> -p '{"spec":{"claimRef": null}}'

The PV will transition to Available and can be bound to a new PVC.

Warning: This may expose data from the previous claim.

For dynamic provisioning failures, check the CSI driver or provisioner logs:

# Find the provisioner pods
kubectl get pods -n kube-system | grep -E 'csi|provisioner'

# Check logs
kubectl logs -n kube-system <provisioner-pod> --tail=100

Look for quota errors, permission issues, or backend connectivity problems.

If the PVC is fundamentally broken, recreate it:

# Backup the PVC spec
kubectl get pvc <pvc-name> -o yaml > pvc-backup.yaml

# Delete the broken PVC
kubectl delete pvc <pvc-name>

# Remove any claimRef and status from backup, then recreate
kubectl apply -f pvc-backup.yaml

Note: With Delete reclaim policy, deleting PVC also deletes the PV and data.