ArgoCD 1.5 - Move to upstream helm charts when Argo supports Helm3 and move forks when routes are fixed upstream

[springdo]

To be moved:

• move argocd to upstream chart or the operator
• move zalenium to upstream chart once PR is merged
• move sonarqube to upstream chart
• move wekan to upstream chart once PR is merged
• move CRW to proper repo

FYI - @ckavili and @eformat

[springdo]

@eformat has begun this work with his PR #81

[eformat]

argocd - operator in bootstrap - #83

[ckavili]

Raised a pull request to Zalenium for updating apiVersion for route. When it's merged, we can start using upstream one for it too 🙃

[springdo]

zalando/zalenium#1175

[jtudelag]

I would propose to move to OpenShift Gitops Operator instead of the Upstream ArgoCD Operator. Opinions @ckavili @eformat @springdo ?

[eformat]

looks like we have productized/forked the upstream chart we are currently using?

community operator we are using:
https://github.com/argoproj-labs/argocd-operator

redhat operator:
https://github.com/redhat-developer/gitops-operator

many of the same RH's are commiting to both .. the argoproject looks upstream ? although not sure about that ...

until DEX/SSO supported .. we should stick with the one we have i think ?