Goal

As an OSD/ROSA dedicated admin, I want to enable team to be deploy Argo CD by installing OpenShift GitOps operator through the OperatorHub in a custom namespace (not openshift-gitops) so that I can configure the operator based on my own requirements.

The access model on OSD and ROSA entails that customers (dedicated-admin) do not have read or write access to layered products namespaces (e.g. openshift-gitops) namespace:
https://docs.openshift.com/rosa/rosa_policy/rosa-policy-process-security.html#rosa-policy-rh-access_rosa-policy-process-security

The consequence is that while dedicated-admin can install the operator on their own from OperatorHub, they are not able to make any modifications to the operator configurations and other CRs (e.g. default ArgoCD CR in openshift-gitops namespace) in the layered products namespaces.

Acceptance Criteria

• OSD and ROSA customers can install OpenShift GitOps operator in custom namespaces
• The OpenShift GitOps operator behaviour remains the same when customers install it in custom namespaces
  • The default Argo CD instance monitoring remains integrated with OpenShift cluster monitoring stack