Unavailable BSL is still functional for backup / restore

[danfengliu]

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.

Spec:
  Default:  true
  Object Storage:
    Bucket:  test-1
  Provider:  gcp
Status:
  Last Synced Time:      2024-05-09T08:28:24Z
  Last Validation Time:  2024-05-09T08:27:44Z
  Message:               BackupStorageLocation "default" is unavailable: Backup store contains invalid top-level directories: [dir-1]
  Phase:                 Unavailable

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 to velero 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> or kubectl get backup/<backupname> -n velero -o yaml
• velero backup logs <backupname>
• velero restore describe <restorename> or kubectl get restore/<restorename> -n velero -o yaml
• velero restore logs <restorename>

Anything else you would like to add:

Environment:

• Velero version (use velero version):
• Velero features (use velero client config get features):
• 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.

• :+1: for "I would like to see this bug fixed as soon as possible"
• :-1: for "There are more important bugs to focus on right now"

[blackpiglet]

Two points need discussion in this issue. https://github.com/vmware-tanzu/velero/blob/7563a453fb962382c7b1c456ddb2a6645cdd9493/pkg/persistence/object_store_layout.go#L32-L50

• Whether the backup repository layout change logic still is needed? The layout-checking logic is introduced in issue #576. That issue is used to integrate the Restic repository into the Ark repository. The original issue of the checking doesn't exist anymore, but the data integration check is still valuable.
• Whether the backup and restore associated with that BSL should be processed when the BSL is in an unavailable state?

[blackpiglet]

The agreement of the Velero team is making the Unavailable BSL stop from taking backup and restore.

[vitalii-buchyn-exa]

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.

[blackpiglet]

Sure. You can create a new BSL for the backup. You can ignore the top-level directory by specifying a sub-prefix for the BSL. https://github.com/vmware-tanzu/velero/blob/a8d77eae959e17138845d81997291b6cf43a514d/pkg/apis/velero/v1/backupstoragelocation_types.go#L139-L151