-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Unavailable BSL is still functional for backup / restore #7785
Comments
Two points need discussion in this issue. velero/pkg/persistence/object_store_layout.go Lines 32 to 50 in 7563a45
|
The agreement of the Velero team is making the Unavailable BSL stop from taking backup and restore. |
Hello community, Experiencing the same issue. What if I want to use a bucket for another backups? Can I configure Velero to ignore unknown top level directories? Or maybe specify an ignore list? Thank you. |
Sure. You can create a new BSL for the backup. velero/pkg/apis/velero/v1/backupstoragelocation_types.go Lines 139 to 151 in a8d77ea
|
What steps did you take and what happened:
A GCP bucket BSL is Unavailable, but backup / restore is still functional well.
The reason is I had a top-level directory named dir-1.
What did you expect to happen:
Since other top-level directories do not effect backup/restore, why check that?
The following information will help us better understand what's going on:
If you are using velero v1.7.0+:
Please use
velero debug --backup <backupname> --restore <restorename>
to generate the support bundle, and attach to this issue, more options please refer tovelero debug --help
If you are using earlier versions:
Please provide the output of the following commands (Pasting long output into a GitHub gist or other pastebin is fine.)
kubectl logs deployment/velero -n velero
velero backup describe <backupname>
orkubectl get backup/<backupname> -n velero -o yaml
velero backup logs <backupname>
velero restore describe <restorename>
orkubectl get restore/<restorename> -n velero -o yaml
velero restore logs <restorename>
Anything else you would like to add:
Environment:
velero version
):velero client config get features
):kubectl version
):/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.
The text was updated successfully, but these errors were encountered: