OLM should allow operators to configure their CSV to allow all resources installed by OLM to be deleted upon removal of the operator.  In addition to that, OLM should allow the CSV to be configured to prevent the operator from being deleted until all CRs it is managing have been deleted from the cluster.

Aside from general usability, there are a few issues that create special problems for users:

• Operators that register finalizers on resources require users to remove the finalizer before the resource can be deleted.
• Resources based on CRDs that define multiple versions with conversion webhooks cannot be accessed because the operator is missing.
• The above can lead to failures when users attempt to reinstall the operator, which produce error messages that don't allow users to easily identify the source of the problem.

Note, the existing behavior (not deleting anything) is by design.