[WIP] Decouple OperandConfig controller from OLM #1191
+746
−9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it: CPD testing of argoCD based deployments on CNCF clusters were blocked due to the error in the first comment found repeating in the ODLM logs. This signaled that the operandconfig controller was not completely decoupled from OLM based on its reliance on finding the subscription and csv for an operator in order to update the operandconfig status. I more or less mirrored the changes to the operandrequest controller by shifting focus from sub and csv to deployment. There is less to update in operandconfig than there was in operandrequest so I am not as sure about having a totally separate controller again but that was the my best bet given the time. Open to suggestions for improvement.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
Release note: