The http: was a command I had copied from the wrong terminal window, so I have been using https: for the join command. Version Sha: 7738ec5d0d6f5bf94a809ee0f6ff0142cfa525a6Īny ideas what could be wrong?! I hope someone can specify exactly which IPs I should use. This is output of my Vault Server configuration values: => Vault server configuration: VAULT_CACERT: "/vault/userconfig/vault-server-tls/vault.ca" Tls_client_ca_file = "/vault/userconfig/vault-server-tls/vault.ca"Īnd these are my extra env. Tls_key_file = "/vault/userconfig/vault-server-tls/vault.key" Tls_cert_file = "/vault/userconfig/vault-server-tls/vault.crt" in the VAULT_ADDR, address=, cluster_addr= and so on.Ĭan someone explain exactly which IPs or FQDNS should be used? I’m getting blind at the moment and have no idea anymore. I have tried tons of different IP addresses etc. * failed to join raft cluster: timed out on raft join: %!w() My problem is that I can’t join a pod to raft: ❯ kubectl -n vault exec -ti vault-1 - vault operator raft join Įrror joining the node to the Raft cluster: Error making API request. I have verified that the vault.ca, vault.crt and vault.key files have been mounted inside the pods, and that the SAN names are present in those files. Subject Alternative Names: vault, vault.vault,, .local, vault-0.vault-internal, vault-1.vault-internal, vault-2.vault-internal, IP Address:127.0.0.1 I am trying to setup Vault in HA mode with Raft storage and TLS using certs from my own CA (pfSense) and I created a certificate for Vault with the following info: Hi! I’m usually not the one that begs for help in these forums, but I just have to admit that I am stuck and need assistance!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |