velero: failed to restore volume with StorageClass, claim Selector is not supported
What steps did you take and what happened: We have a setup where the NFS CSI driver creates the PV’s dynamically once the PVC’s are created/restored. This is done by specifying the correct storage classes.
However, when Velero backs up the PVC’s, it adds a selector that breaks the PV creation by the NFS driver:
selector:
matchLabels:
velero.io/dynamic-pv-restore: <pvc-name>.87z5b
What did you expect to happen: We expect the restore to happen without Velero adding extra selectors that break the dynamic PV creation.
The output of the following commands will help us better understand what’s going on:
velero backup create BACKUP_NAME --include-namespaces NAMESPACE --snapshot-move-data --snapshot-volumes --include-resources pvc
velero restore create --from-backup BACKUP_NAME
Environment:
Velero helm chart 6.4.x, Velero version 1.13.2 Kubernetes version 1.27
Note, this is a duplicate of this issue on the helm chart, but I think it belongs here
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 23 (9 by maintainers)
A tentative ETA is by the end of Aug.
Though I don’t have enough information to confirm, I think the failures mentioned in this issue are most likely caused by issue #7898. So please check Velero logs or DataUpload/DataDonwnload CR status, if you see a message similar to below example, the problem will be fixed by #7898:
The
claim Selector is not supportedmessage in the PVC is not an error, but an expected behavior.For the volume-only restore, Velero data mover restore at present only supports
Immediatevolumes; there may be a way to go better with WaitForFirstConsumer volumes which will be implemented in future releases see #8044It seems very unlikely to me that something as large and common as csi nfs would be “faulty”.