-
Notifications
You must be signed in to change notification settings - Fork 5
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
Control over general Velero Backup/Restore Spec that gets exposed or allow listed via NAB/NAR CRD spec. #37
Labels
Comments
Might need some design, current approach of accepting values from cm is added in main deisgn |
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
@mateusoliveira43 Done, updated |
This was referenced Nov 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: