1. Proposed title of this feature request

Advanced control of OpenShift GitOps operator permissions

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

Currently, there is no way to configure an openshift-gitops instance to prevent it from pruning or deleting most resources in a cluster it manages.

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

Some customers have internal policies that requires them to never delete resources from their cluster. Resources are either updated or marked as "retired" and "deprecated" when no longer required. As such, they need to ensure that OpenShift GitOps and its ArgoCD instance will never be able to prune or delete resources on its own.

4. List any affected packages or components.

OpenShift GitOps Operator, ArgoCD