Repository navigation
Non-Admin backup/restore operations performance #30
shubham-pampattiwar
started this conversation in
General
Replies: 3 comments
|
Hopefully upgrades can be done across multiple veleroes around the same time with no crd conflict. Maybe guidance to pause all schedules and wait till all backups complete b4 upgrade. |
0 replies
|
I'm not familiar with the design of Velero or OADP, but from the sound of it, it seems that the Velero limitation is the one that should be fixed. Having each user install their OADP sounds like a handful. Regardless of the implementation, we must not let a namespace-specific backup DoS a cluster-wide one. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Due to the current limitation that a single instance of velero processes one single backup/restore request at a time, the non-admin backup/restore ops would not be performant.
As an alternative multiple instance of OADP with NAC deployment can be considered to address the performance concerns (Given that each NAC instance will be tied to one OADP Operator instance i.e OADP:NAC :: 1:1)
All reactions