Documentation: Recommended deployment model when using the Red Hat GitOps Operator on OpenShift

1) What is the nature and description of the request?
Gitops Operator deployment in the openshift-gitops namespace workflow and supported configuration that can be done against the default deployment options.
Document Configuration of Operator in the openshift-gitops namespace vs deploying instances in other namespaces for Application

2) Business requirements
Clarification in Red Hat Gitops documentation: no clarity around supported use cases when deploying Operator, from an administrator point of view (managing the Operator lifecycle, deployment options, and environment vars. (i.e DISABLE_DEFAULT_ARGOCD_INSTANCE variable for GitOps Operator subscription).

3) How would you like to achieve this? (List the functional requirements here)
Have supported ENV vars to Red Hat GitOps Operator installation to the main documentation (https://docs.openshift.com/container-platform/4.10/cicd/gitops/installing-openshift-gitops.html) and describe what each of these does and when they can/should be used (use cases)

6. For each functional requirement listed, specify how Red Hat and you can test to confirm the requirement is successfully implemented.

Lacking proper documentation around the supported env variable in the main OpenShift docs, update the docs to include use case examples and examples when installing the Red Hat GitOps Operator from the OpenShift CLI.

7. Would you be able to assist in testing this functionality if implemented?
Yes