Design: read in velero server arg options and make them available to OADP
weshayutin opened this issue · comments
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
@kaovilai I think you wanted me to open this a while back, can you please add some details to the description
Server args were requested by @shubham-pampattiwar in https://issues.redhat.com/browse/OADP-1182
It might've been my bad judgement but due to current dpa fields affecting server args indirectly via the install.Deployment (pkg), and we had wanted full control, I made a new path to forming velero container server args rather than making it fully compatible and interoperable with the OADP 1.1 fields. Split brain syndrome.
The cleanest way to approach this would be to make sure all args are implemented as a podTemplateOption which we could then refactor dpa from 1.3 format to 1.4 format which would eliminate the split brain but requires refactoring of dpa perhaps.