Open nia-potato opened 1 year ago
You have not mentioned which seal method is in use for this Vault. A new node requires access to the unseal key to join the cluster, which may mean manual unsealing.
A Raft cluster of 6 nodes is questionable, since it is no more fault-tolerant than a 5 node cluster. The failure tolerance is 2 in both cases.
I'm pretty sure the autopilot settings in the configuration file only apply when initializing a new cluster, and to modify an existing cluster, changes must be made via the Vault API.
Describe the bug after raising replica and min_quorom to 6 in the helm chart, running k get pods only shows 5 pods are ready instead of joining the 6 pod to raft.
To Reproduce Steps to reproduce the behavior: install chart with config of
Other useful info to include: vault pod logs,
kubectl describe statefulset vault
andkubectl get statefulset vault -o yaml
outputExpected behavior replica of 6 + min_quorum of 6 should have 6 nodes all in ready state and joined in raft.
Environment