Prevent operator removal, while it still has some CR's to manage

[rhopp]

Currently, when there is a checluster CR with oAuth enabled, it has oauthclients.finalizers.che.eclipse.org finalizer. This means, that this CR is not possible to delete until this finalizer is removed.
This has a good reason: eclipse-che/che-operator#11

But it introduces another problem: When the che-operator is deleted before CR is deleted, this CR remains there and it's not possible to delete it (without some workarounds).
This is mostly notable, when CRW is deployed with Openshift oAuthSupport and user then tries to delete whole namespace, where CRW is deployed (together with the operator) -> everything is deleted, but for the checluster CR, which prevents the namespace from deletion.

I was thinking... couldn't che-operator be aware of how many checluster CRs is it managing and maybe have it's own finalizer if the number is greater than 0? That would mean it would be also impossible to delete che-operator before removing all its managed CRs.

Is something like that possible, @davidfestal ? Or do we have to provide some instructions on how to delete CRW deployment (or maybe some uninstall script)?

[dmytro-ndp]

Command to remove CheCluster custom resource with finalizer:
oc patch checluster codeready -p '{ "metadata": { "finalizers": null }}' --type merge -n ${CHE_OPENSHIFT_PROJECT}

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.