1. Proposed title of this feature request

Add ordered deletion functionality to OLM managed operators

2. What is the nature and description of the request?

This request is to enable operator authors who need to perform some cleanup on their OLM-managed operators are able to successfully do so. There are several documented cases both upstream and downstream where the operator's RBAC is removed from the cluster before the operator itself is able finish it's deletion routine. This causes errors during operator deletion and the operator may not be able to cleanup after itself.

Deletion ordering is not an easy thing to implement in kubernetes. There are tools like finalizers which can help, but it's not clear how to use those within OLM to achieve an ordered deletion. 

Here are some cases of customers affected by this issue:

https://bugzilla.redhat.com/show_bug.cgi?id=2058048

https://github.com/operator-framework/operator-lifecycle-manager/issues/2235

A potential feature would allow for customized deletion logic added to OLM, where an operator author could opt-in to an OLM finalizer to ensure that the operator deletion is what they expect.

3. Why does the customer need this? (List the business requirements here)

The customer should be able to rely on an ordered tear down of their operator and ensure that there are no orphaned resources left on the cluster. OLM exposes a lot of knobs for delivering the operator onto the cluster, but none for how the removal process should look like.

4. List any affected packages or components.

OLM, operators