Open shubham-pampattiwar opened 7 months ago
Lets target for this phase 1 with an optional cluster-wide BSL usage flag.
Additional responsibilities of the controller:
Velero Backup spec has the field storageLocation
(and current NonAdminBackup also has it). Should we put some validation or even remove that field from NonAdminBackup :question: My fear is that non admin user can use a admin BSL for backups.
I think this is not https://github.com/migtools/oadp-non-admin/issues/37 responsibility, because this should be a always active check, and not only admin user turns it on.
Maybe add to OADP DPA which BSL NAC will use (bad UX if NAC is used by many non admin users :question:) or with this feature, only allow NonAdminBackups if a NonAdminBackupStorageLocation exists and add a field in NonAdminBackup spec and remove storageLocation
from backupSpec
.
Add the the functionality of providing the non-admin users the ability to create their own BackupStorageLocations. In other words BYOB (Bring your own Bucket/BSL). The task would entail: