1. Proposed title of this feature request
Inject configured OpenShift Container Platform 4 - PKI into repo-server to trust private repositories

2. What is the nature and description of the request?
Currently, users that are adding a private git repository are also required to add the respective Certificate Authority (CA) using either the Web-UI or CLI to establish chain of trust on TLS level (see https://argo-cd.readthedocs.io/en/stable/user-guide/private-repositories/ for details). Considering that in most cases the CA would be available already in OpenShift Container Platform 4, via the configrued PKI it would very much improve the developer/user experience when those certificates are automatically made available to repo-server so that trust is automatically established and no additional steps need to be taken (only if the certificates used are not part of the OpenShift Container Platform 4 - PKI).

3. Why does the customer need this? (List the business requirements here)
Currently all users of GitOps/ArgoCD are required to provide the required certificates when adding a provate git repository to establish certificate chain of trust. Considering that the PKI would actually be known when running on OpenShift Container Platform 4 it would be nice if the same is either automatically mounted to the repo-server or at least functionality is available to make it easily available (for example with https://docs.openshift.com/container-platform/4.11/networking/configuring-a-custom-pki.html#certificate-injection-using-operators_configuring-a-custom-pki).

4. List any affected packages or components.
Red Hat OpenShift GitOps / ArgoCD