Argo-cd: How to disable tls for the purpose of own tls termination on tls proxy ?
Describe the bug
Hey, maybe this is the right place for this : https://github.com/argoproj/argo-helm/issues/168
To Reproduce
Install argo-cd and try to splice it with letsencrypt over for example trafik reverse proxy
sokoow
All 5 comments
Does this help?
alexec
on 22 Nov 2019
Nope, sorry it doesn't @alexec :/
sokoow
on 4 Dec 2019
By default the ingress forward traffic to ArgoCD using HTTP
You can change it to HTTPS but then the Ingress is not happy with ArgoCD self-signed cert.
rocketspacer
on 18 Feb 2020
Are there any workarounds for this?
We are using TLS termination on a separate ingress controller, all certs are managed there, hence we don't want to share any certs with ArgoCD.
Passthrough with self-signed autogenerated certs on ArgoCD leads to browser alerts.
Is there any particular reason why we don't have optional TLS on the ArgoCD side? Why does the app care about the infrastructure layer?
bbl
on 23 Apr 2020
My issue was I had TLS termination at the load balancer and then all traffic was sent over http to argo cd. Argo CD doesn't like that and expects traffic to be on 443. The workaround is to use the --insecure flag. In the helm chart I used here it is on of the first things in the repo 馃う . RTFM
eshaffer321
on 4 Jan 2021
Related issues
travis-sobeck
路
3Comments
moensch
路
3Comments
clintberry
路
3Comments
gregsheremeta
路
3Comments
turbotankist
路
3Comments
Most helpful comment
Are there any workarounds for this?
We are using TLS termination on a separate ingress controller, all certs are managed there, hence we don't want to share any certs with ArgoCD.
Passthrough with self-signed autogenerated certs on ArgoCD leads to browser alerts.
Is there any particular reason why we don't have optional TLS on the ArgoCD side? Why does the app care about the infrastructure layer?