How to avoid setting up credentials in private repo for each Argo Application?

[cnukwas]

Hi,

Our internal github requires AD/LDAP users login, even to view any repositories, so wondering how application teams should set up Argo repository connections for each Argo Application for Kubernetes/OpenShift deployment.
Users are able to view and clone any repositories once he/she is logged in, but not otherwise.
Would like to avoid individual user credentials input for setting up a repo connection since Kubernetes secrets are not encrypted(cluster and Argo admin is controlled, we still don't users credentials stored by Argo Configmap or Secrets).

Are there any workarounds or solutions to avoid either credentials or SSH keys input for each team and application repository, but still allow the teams to use a repo for Application configuration?

I came across Credentials templates, which may help if all the repositories under the same org/tree structure. Did anyone run into a similar situation as above and any input?

Thanks