Backup storage location removed and old backups/repositories still in K8S

[dk-it-consultant]

Hi,

I am new to velero and I am trying to understand something.
I have inherited a k8s cluster that runs velero 1.16 and it is reporting a lot of "storage location not found errors"
backupRepo=velero/full-backups-restic-cksvq error="BackupStorageLocation.velero.io \"full-backups\" not found"

The actual location (and thus the data) is already gone as well. These refer to backups from over a year ago and we currently only keep 90 days. Also the BSL custom resource is gone from the cluster. Only the current location is there.

As I understand from the docs velero uses the actual storage as it's source of truth. However in our cluster, we still have these old Backup custom resources pointing to the non existing BSL. We also still have BackupRepository custom resources that point to the removed BSL. And we still have some ResticRepository custom resources that also refer to the removed BSL.

So in short, we have 3 custom resources (Backup, BackupRepository, ResticRepository) that point to an non existent BackupStorageLocation that has been deleted from the cluster and the actual data is also gone from our (S3) storage.

I would like to know if it is save to just delete these resources from the cluster and if there is something else I can do to make velero happy again.

Thanks,

Danny

[kaovilai]

Given BackupStorageLocation.velero.io \"full-backups\" not found you are safe to delete any resources mentioning full-backups BSL.

We do not auto delete CR from cluster resources pointing to non-existent BSL atm IIUC.