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
We are planning to move from pulp runinng on a VM to operator in openshift . From infrastructure as a code perspective , it would be great to control the repoistory actions like creating syncing and all also via openshift resources . If not separate automation tool has to be used for maanging repository part alone .
The text was updated successfully, but these errors were encountered:
We had an internal discussion about this issue and, for now:
we still have no consensus if the operator should do it (in my opinion, this is a good idea and a nice to have feature for the operator)
we don't have enough bandwidth to work in it yet (depending on the level of the automation that we'd like to achieve, it will probably be very complex to code it)
With that being said, we are going to let this issue open and will revisit it later (but no promises with dates), ok?
We are planning to move from pulp runinng on a VM to operator in openshift . From infrastructure as a code perspective , it would be great to control the repoistory actions like creating syncing and all also via openshift resources . If not separate automation tool has to be used for maanging repository part alone .
The text was updated successfully, but these errors were encountered: