VolumePolicy support for Phase condition of PVC to allow skipping Pending PVCs #7233
Description
Describe the problem/challenge you have
Backup namespace contains PVCs which not in used by any pod, then got PartiallyFailed result.
k get pvc -n azure-csi-test
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
nginx-logs-e2e-1 Bound pvc-e4dda753-8c88-4194-93b5-959a01be1de4 1Gi RWO managed-csi 16h
nginx-logs-e2e-2 Pending managed-csi 16h
nginx-logs-e2e-3 Pending managed-csi 16h
nginx-logs-e2e-4 Pending managed-csi 16h
nginx-logs-e2e-5 Pending managed-csi 16h
velero describe backup backup-csi-6 --details
Name: backup-csi-6
Namespace: velero
Labels: velero.io/storage-location=default
Annotations: velero.io/resource-timeout=10m0s
velero.io/source-cluster-k8s-gitversion=v1.28.0
velero.io/source-cluster-k8s-major-version=1
velero.io/source-cluster-k8s-minor-version=28
Phase: PartiallyFailed (run `velero backup logs backup-csi-6` for more information)
Errors:
Velero: name: /nginx-logs-e2e-2 message: /Error backing up item error: /error executing custom action (groupResource=persistentvolumeclaims, namespace=azure-csi-test, name=nginx-logs-e2e-2): rpc error: code = Unknown desc = PVC azure-csi-test/nginx-logs-e2e-2 has no volume backing this claim
name: /nginx-logs-e2e-3 message: /Error backing up item error: /error executing custom action (groupResource=persistentvolumeclaims, namespace=azure-csi-test, name=nginx-logs-e2e-3): rpc error: code = Unknown desc = PVC azure-csi-test/nginx-logs-e2e-3 has no volume backing this claim
name: /nginx-logs-e2e-4 message: /Error backing up item error: /error executing custom action (groupResource=persistentvolumeclaims, namespace=azure-csi-test, name=nginx-logs-e2e-4): rpc error: code = Unknown desc = PVC azure-csi-test/nginx-logs-e2e-4 has no volume backing this claim
name: /nginx-logs-e2e-5 message: /Error backing up item error: /error executing custom action (groupResource=persistentvolumeclaims, namespace=azure-csi-test, name=nginx-logs-e2e-5): rpc error: code = Unknown desc = PVC azure-csi-test/nginx-logs-e2e-5 has no volume backing this claim
Describe the solution you'd like
-
[discarded] Warning should be enough to let user notice this workload might have issue or not.
-
We could introduce ability to skip unbound PVCs through new volume policy actions https://velero.io/docs/main/resource-filtering/#supported-volumepolicy-actions
Anything else you would like to add:
Environment:
- Velero version (use
velero version): - Kubernetes version (use
kubectl version): - Kubernetes installer & version:
- Cloud provider or hardware configuration:
- OS (e.g. from
/etc/os-release):
Vote on this issue!
This is an invitation to the Velero community to vote on issues, you can see the project's top voted issues listed here.
Use the "reaction smiley face" up to the right of this comment to vote.
- 👍 for "The project would be better with this feature added"
- 👎 for "This feature will not enhance the project in a meaningful way"