You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Velero Backup CR/Restore CR consists of a plethora of Backup/Restore Spec options. It might be desirable to have a control over the spec that is exposed or may be allowlisted for non-admin users.
For instance, Backup Spec IncludedNamespaces should by default be the non-admin user's namespace as this is a scoped backup operation
Another instance is mentioned in the relevant discussion of cluster admins wanting to set a default backup TTL for all the non-admin users
Or maybe the cluster-admins want to enforce that only fs-backups should be used for volumes, so defaultVolumesToFSBackup should be true for all non-admin backups
The text was updated successfully, but these errors were encountered:
As mentioned in #35, this also needs to apply to Restore specs
@shubham-pampattiwar can you please update issue title to reflect this (or better to have one issue per object?)
shubham-pampattiwar
changed the title
Control over general Velero Backup Spec that gets exposed or allow listed via NAB CRD spec.
Control over general Velero Backup/Restore Spec that gets exposed or allow listed via NAB/NAR CRD spec.
Apr 17, 2024
The Velero Backup CR/Restore CR consists of a plethora of Backup/Restore Spec options. It might be desirable to have a control over the spec that is exposed or may be allowlisted for non-admin users.
IncludedNamespaces
should by default be the non-admin user's namespace as this is a scoped backup operationdefaultVolumesToFSBackup
should be true for all non-admin backupsThe text was updated successfully, but these errors were encountered: