search

mintel / dex-k8s-authenticator

A Kubernetes Dex Client Authenticator
MIT License
374 stars 146 forks source link

k8s_ca_pem_base64_encoded not used? #172

Open Taragos opened 3 years ago

Taragos commented 3 years ago

Hello,

I recently deployed the K8S Authenticator in our environment and it is working pretty good. The only issue I have is with supplying the CA PEM in base64 encoded format.

When trying to supply it via k8s_ca_pem_base64_encoded I would have expected an option that sets the certificate-authority-data field to the given Base64 encoded Value. But this is not the case for my instance. (Supplying the Certificate via one of the other Options works fine but I personally don't like the approach of not having the certificate in my kubeconfig as it is another component one has to look out for)

efossas commented 2 years ago

it appears that feature was added to master with this PR (06/15/2021): https://github.com/mintel/dex-k8s-authenticator/pull/171

but the last release was v1.4.0 back in 12/16/2020 and doesn't include this feature yet.

you can update your image to: docker.io/mintel/dex-k8s-authenticator:latest, and it should work (just tested and it did). not a fan of using "latest", but not sure what the process is for new releases.

looks like @nabadger creates all of the releases.