[RFE] OLM deletes Operands upon Operator removal #1787
Labels
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone
Feature Request
Is your feature request related to a problem? Please describe.
As a cluster-admin I can instruct OLM that I want to remove all Operands before removing the Operator, so that I don't end up with orphaned workloads.
Why is this important:
Orphaned workloads are hard to clean up. After the Operator has been removed deleting the custom resource does not clean up secondary resources. It can be hard to find these resources as there is no obligation to put owner references or labels to them. It is probably impossible to find when those resources are outside of the cluster.
Describe the solution you'd like
The Operand removal should have timeoutHitting the Operand removal timeout should NOT fail Operator removalHitting the timeout should create an alert eventThe text was updated successfully, but these errors were encountered: