-
Notifications
You must be signed in to change notification settings - Fork 360
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Velero backup is failing partially with pod volumes have no associated PVCs errors #607
Comments
I see the same issue. Backup works fine without a
Version:
After updating to v1.14.1 this seems to work fine. Seems relates to vmware-tanzu/velero#7929 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
emptyDir
volume 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/LinuxThe text was updated successfully, but these errors were encountered: