-
Notifications
You must be signed in to change notification settings - Fork 878
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
Vault agent injector throws error 'tls: bad certificate' after each 24 hours #787
Comments
@swenson Found the same bug, but I'm experiencing still the same issue |
@lucasscheepers I could be wrong, but it looks like you're specifying the |
Oh yeah forgot to close this issue. I specified indeed the wrong release of the vault agent injector |
the same problem exists in 0.22.1 |
Seems Vault v1.15.2 (cf1b5cafa047bc8e4a3f93444fcb4011593b92cb), built 2023-11-06T11:33:28Z still exists? |
Nasty solution for local development - killing the pod kubectl -n vault delete pod -l app.kubernetes.io/name=vault-agent-injector |
Description of the bug
I've deployed Vault successfully with the vault-agent-injector. I enabled the auto-tls feature, but I've experiencing some sporadic tls issues. I've re-deployed Vault multiple times when I got the
tls: bad certificate
error and after each re-deploy the vault-agent-injector did work again. But after 24 hours it returns the same error again and again.I'm aware of the auto-tls feature bug, but I'm using the helm chart version 0.20.1 and only have one replica. I've read about people experiencing this bug with 2 or more replica's and using the helm chart version below 0.16.1.
These are the logs of the vault-agent-injector:
The
values.yml
file looks like this:The text was updated successfully, but these errors were encountered: