Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

k8s_ca_pem_base64_encoded not used? #172

Open
Taragos opened this issue Jul 7, 2021 · 1 comment
Open

k8s_ca_pem_base64_encoded not used? #172

Taragos opened this issue Jul 7, 2021 · 1 comment

Comments

@Taragos
Copy link

Taragos commented Jul 7, 2021

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
Copy link

efossas commented Apr 4, 2022

it appears that feature was added to master with this PR (06/15/2021): #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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants