You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ kubectl exec -it vault-0 -n vault-foo – /bin/sh
Unable to use a TTY - input is not a terminal or the right kind of file
error: unable to upgrade connection: container not found ("vault")
$ kubectl exec -i -t vault-0 -n vault-foo – ls /vault/userconfig/vault-server-tls
Unable to use a TTY - input is not a terminal or the right kind of file
error: unable to upgrade connection: container not found ("vault")
but the pods are installed
$ kubectl get pods -n vault-foo
NAME READY STATUS RESTARTS AGE
vault-0 0/1 CrashLoopBackOff 5 3m36s
vault-1 0/1 CrashLoopBackOff 5 3m36s
vault-2 0/1 CrashLoopBackOff 5 3m36s
vault-agent-injector-d54bdc675-79ll7 1/1 Running 0 3m36s
what I'm missing here?
The text was updated successfully, but these errors were encountered:
Hi @meiry, I really feel your pain, just had the same error.
The issue is as follows. You specify leader_ca_cert_file (incl. key and ca) in the retry_join, but have TCP listener which has TLS enabled by default, tls_disable=false, because you commented the line with #tls_disable = 1, where you probably intended to disable TLS previously.
Now, the error message is actually correct: open : no such file or directory
The path for the TLS file is empty (open :), because not specified.
To fix the issue, I had to add the following lines:
Describe the bug
I created k8s secret and followed the manual on how to create TLS certificates
first, i create the secret in k8s then
i deploy vault with ha configuration and raft storage
bug pods are with error that looks like this :
Steps to reproduce the behavior:
Environment
Chart values:
The dockers are not started as I'm getting :
but the pods are installed
what I'm missing here?
The text was updated successfully, but these errors were encountered: