ngarafol

You can try entering container and apt update; apt install ca-certificates; docker stop container; docker start container. Fixed the issue for me!

I had to do more modifications. If I do as @jasonodonnell proposed, hostname is not getting substituted, so vault status reads: ``` / $ vault status Key Value --- -----...

Hi @webmutation. This issue is based on instructions from @jasonodonnell listed here https://github.com/hashicorp/vault-helm/issues/40 Basically, you need vault-helm master and pull files from https://github.com/hashicorp/vault-helm/pull/58 and merge locally. I am using transit...

@catsby Not 100% sure but thinking aloud, removing raft peer is not necessary here. I wanted peer with same id (and new ip) to return to cluster. If you remove...

Auto rejoin works for me, as I said. Deleted node (pod) and new node (pod) automatically rejoined since by raft_id its the same node...

@fewknow Thanks for sharing, but I think your issue is more related to cluster being sealed. Original issue I had (OP) was that raft rejoin would not work on already...

It does not work. I can share my stations privately?

I sent you mail to gmail

@tuttheking81 did you want to write something?

There is something wrong with PushSecret definitely. Vault version used is 1.7.2, ESO is v0.9.11. I noticed there is pushsecret fix for vault added to v0.9.14 so will try that...