-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(uninstall): rely on OLM to delete operator resources via CSV deletion #27
fix(uninstall): rely on OLM to delete operator resources via CSV deletion #27
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 small issues
fdc63c0
to
30ee369
Compare
30ee369
to
e770ac4
Compare
e770ac4
to
0f2ab2d
Compare
0f2ab2d
to
8e8b0a7
Compare
Based on some discussion with the OLM team, I think we can immediately improve on solving this problem by ignoring the install plan altogether and deleting only the CSV and CRDs. We can lookup the CSV using And then lookup the CRDs from |
8e8b0a7
to
494ed0d
Compare
494ed0d
to
01823b2
Compare
When multiple install plans are present for single operator, select the resources of install plan containing the installed CSV while uninstalling the operator.
01823b2
to
6ea2e2c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
These suggestions were incorporated.
When multiple install plans are present for single operator,
select the resources of install plan containing the installed CSV
while uninstalling the operator.