As a Red Hat Open Shift user who would like to use Git Ops, I am frustrated by the lack of configuration documentation, the unexplained lack of support for official tooling and the poor in-platform guidance. 

As a long time ArgoCD user, I am very comfortable in advanced configuration and usage, but am unable to bring that experience to bear with my current projects.

I would like to see much better documentation around how to use Open Shift GitOps, as the current documentation and examples are extremely high level and to be blunt, not helpful.

What would be useful:

• How to manage git/helm repos via the CLI or configmaps, or whatever the 'correct' way is.
  •  Critical: must have the ability to manage with self-signed certificates
  • This is my current primary frustration - I have a helm repo, hosted on a server with a internal CA - I have added the relevent certs to ArgoCD's Repository certificates & known hosts, but when adding the repo I still get x509 invalid cert issues. There is no way to add a repo while ignoring the cert, which I COULD do with `argocd repo add https://repo.tld --insecure-skip-server-verification` but since y'all don't support that, I cannot proceed. I cannot accomplish my task and have no workaround documented.
• How to deploy complex helm based applications using the Operator. I know how to do this, but trying to deploy an app via the operator is seriously confusing and frustrating for someone who knows  what they're doing, I couldn't imagine being new to ArgoCD/GitOps.
• More than one [happy-path springboot|https://docs.openshift.com/gitops/1.11/argocd_applications/deploying-a-spring-boot-application-with-argo-cd.html] install example 
  • Examples of how to use self-hosted helm repos - many people do this
  • Examples of how to use upstream helm repos

I can see the level of effort y'all are putting into OpenShift, and Operators - I'm adding this to help flesh out some scenarios that might not be immediately evident to the PM org - There are lots of organizations who want to use OpenShift/GitOps that are in heavily locked down environments, have internal CA's and restrictive policies on how to get data/resources into those environments. Happy path "everything is available on the internet" is not going to work - please consider users that are on disconnected / restricted environments. Or, tell your sales team to stop selling that  

Please, feel free to reach out if you have clarifying questions - I truely want to see things continue to improve.