Max Bowsher

The situation is now even more confused - a new release `v1.0.1-vault-4` has been made on one side of the divergence, and `v1.0.1-vault-5` has been made on the other!

It might also be worth considering migrating away from vault-java-driver entirely... that project seems to have made some rather odd implementation choices concerning how it handles KV v1 vs v2...

Oh... this one's still open... has it really only been a year since I bumped into it? :-) I'm not really surprised - but yeah, it is incredibly frustrating that...

Could you add some information about the process that was controlling the rolling restart of the Consul server nodes? If it was an external sequencer that was attempting to understand...

Thanks... it seems fairly clear at this point that the default `readinessProbe` in https://github.com/hashicorp/consul-k8s/blob/main/charts/consul/templates/server-statefulset.yaml is insufficient, and needs to be replaced with a custom command that understands that a server...

You literally asked the Vault CLI to return JSON format, so it did... If you don't want it to format the result as JSON, don't ask it to do that.

If you've lost the unseal keys, and you don't have an active running unsealed Vault process, everything has been lost. There's nothing to do other than wipe it all and...

This issue appears to be duplicated in #19342, and I provided an answer there.

The documentation for the `min_quorum` option at https://developer.hashicorp.com/vault/api-docs/system/storage/raftautopilot#min_quorum sounds to me like it is implying that it should be set to the total number of servers, not the desired quorum...

@koen-venly I suggest it would be best if you started a topic in https://discuss.hashicorp.com to talk through your problem in a separate conversation - even though your problem sounds somewhat...