Make cascade deletion optional

[sector2000]

Currently, when the Pattern CR is being deleted, the operator performs a cascade deletion of all ArgoCD Applications and their content (overriding the apps pruning configuration), and all ManagedClusters resources, eventually removing the entire Hub and ManagedClusters custom configurations, and detaching (and potentially deleting) all Openshift managed clusters.

This is a very dangerous behaviour.

For this reason this PR makes this behaviour configurable via the gitops.enableCascadeDeletion parameter in the patterns-operator-config ConfigMap. For a safe and conservative approach, the parameter defaults to false. If the user wants to actually perform cascade deletion, he can just set the parameter to true before deleting the Pattern instance.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sector2000
Once this PR has been reviewed and has the lgtm label, please assign mlabonte-rh for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @sector2000. Thanks for your PR.

I'm waiting for a validatedpatterns member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.