papanito
commented
1 week ago I see the same issue. Backup works fine without a resource-policies though.. My config
chedules:
cluster-backup:
disabled: false
schedule: ${cluster_backup.schedule}
skipImmediately: false
template:
csiSnapshotTimeout: ${cluster_backup.csi_snapshot_timeout}
hooks: {}
includedNamespaces:
- "*"
itemOperationTimeout: ${cluster_backup.item_operation_timeout}
ttl: ${cluster_backup.ttl}
resourcePolicy:
apiGroup: null
kind: configmap
name: velero-resource-policies
useOwnerReferencesInBackup: false
configMaps:
resource-policies:
labels:
velero.io/plugin-config: ""
data:
exclude-storage-policy.yaml: |
version: v1
volumePolicies:
- conditions:
csi: {}
action:
type: snapshot
- conditions:
storageClass:
- smb-csi
action:
type: skip
- conditions:
nfs: {}
action:
type: skip
- conditions:
volumeTypes:
- emptyDir
- downwardAPI
- configmap
- cinder
action:
type: skipVersion:
╰─ velero version ─╯
Client:
Version: v1.14.0
Git commit: 2fc6300f2239f250b40b0488c35feae59520f2d3
Server:
Version: v1.14.0After updating to v1.14.1 this seems to work fine. Seems relates to https://github.com/vmware-tanzu/velero/issues/7929
What steps did you take and what happened: We are trying to update the Velero from v1.13.2 to v1.14.0 and getting some PVC related error while performing the Velero backups. This is working fine on v1.13.2. When I checked some of these pod volumes all of them are using
emptyDirvolume type. I have a resource filtering config map to skip this volume type. On this version it is not working as expected.What did you expect to happen: Velero backup should work without errors. Now it is partially failing.
The output of the following commands will help us better understand what's going on:
Anything else you would like to add: Our resource filtering config map is below.
Environment:
helm version): v3.14.2helm list -n <YOUR NAMESPACE>): 7.0.0 and v1.14.0kubectl version): v1.25.7/etc/os-release): VMware Photon OS/Linux