1. Proposed title of this feature request
Feature-Request: Integration into OpenShift Container Platform - OAuth via Self-Service capabilities

2. What is the nature and description of the request?
In multitenant environment it's important that tenants can setup OpenShift Gitops in self-service manner, meaning everything should be configurable via custom resource definition, triggering the respective Operator to install/configure and setup everything the way it was described in the custom resource. The implementation into the OpenShift Container Platform - OAuth service that is currently available via Configuring SSO for Argo CD on OpenShift is not satisfying this requirement as it's impossible to setup/configure this in self-service manner.

It's therefore requested to simplify the integration into OpenShift Container Platform - OAuth and basically provide this with a custom resource configuration option (such as OpenShiftoAuth: true or similar. With that, everything should be setup accordingly and people from the given namespaces should be able to access the ArgoCD resources with the OpenShift Container Platform - Login.

3. Why does the customer need this? (List the business requirements here)
OpenShift GitOps will be primarily used by either OpenShift Container Platform - Custer Administrator or tenants running on the platform. For tenants it's a hard requirement to be able and setup OpenShift GitOps on their own if needed. It means they need to be able to specify where the GitOps instance should be installed, what namespaces it should cover, etc. To implement proper SSO capabilities, it's required for tenants to attach to OpenShift Container Platform - OAuth to quickly grant access to all users in a given namespace or scope. That way, same credentials can be used and thus adoption will be simplified.

4. List any affected packages or components.
OpenShift GitOps