-
Bug
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
Sprint 61, Sprint 62
Operator deletion should not be possible until all SMCP instances have been removed. Operator removal should then remove all aspects of OSSM and leave no leftover resources.
We should investigate whether OLM supports this. In their docs it says
By design, when OLM uninstalls an operator it does not remove any of the operator’s owned CRDs, APIServices, or CRs in order to prevent data loss. Instead, it is left to the Cluster Admin to remove any unwanted types and resources from the cluster.
We should follow up with them on whether that's still accurate. If so, we can close this as WONTFIX.
- is caused by
-
OPRUN-2640 Delete all resources (CRDs, ServiceMonitor, etc.) associated with an operator install
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-