-
Notifications
You must be signed in to change notification settings - Fork 6
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
fix: mount ca cert also for letsencrypt-staging and parameterize secret key #49
Conversation
Can I have the time to better test this tomorrow before merging? I would like us to consider a bit more before adding a variable to set this, since the thing won't be activated unless one of the two defined cluster issuers is set. So in my view it would be better if each one of the cases has its on secret key instead of allowing the user to set it up. Like having a ternary operator: |
99d02cd
to
05f4da9
Compare
Description of the changes
Currently, ArgoCD's OIDC won't work with
letsencrypt-staging
issuer since it's not issued by a known certificate authority and so ArgoCD return ax509 certificate signed by unknown authority
error when trying to login via Keycloak.To fix that, I added the certificate volume mount to ArgoCD if the issuer is
letsencrypt-staging
. I also parameterized the secret key used in it since in my case it's notca.crt
buttls.crt
(the variable is still default to ca.crt)Breaking change
Tests executed on which distribution(s)