Closed robertgates55 closed 4 years ago
Hi @robertgates55,
I guess this it's a question of where TLS is getting terminated. Are you serving your kube-oidc-proxy without TLS and having it terminated at your ingress controller?
It looks like you'll want to set the certificate authority in your kubeconfig to that of Let's Encrypt's CA.
Thanks Josh - dug a little further & now have it working with a service of type:LB & certs generated with cert-manager (then using the letsencrypt CA to log in as you suggested)
Suggests maybe the docs could do with a little more detail - but happy to close in the meantime.
I've set up kube-oidc-proxy and enabled ingress with cert-manager generating letsencrypt certs for the endpoint. I used the helm chart to deploy.
However, when I try & connect with my generated kubeconfig, the CA obviously doesn't match up - I'm providing the root CA from my EKS cluster (sourced from /var/run/secrets...etc) to an endpoint that's got letsencrypt certs:
What's the correct way to set this up? Is it actually possible to use ingress with ACME certs or is that my issue?