[WIP] Decouple OperandConfig controller from OLM#1191
[WIP] Decouple OperandConfig controller from OLM#1191bluzarraga wants to merge 2 commits intoIBM:masterfrom
Conversation
Signed-off-by: Ben Luzarraga <luzarragaben@gmail.com>
Signed-off-by: Ben Luzarraga <luzarragaben@gmail.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bluzarraga The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Error in ODLM logs:
|
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: