hashicorp / hashicorp/vault-helm
raising replica and min_quorom to 6 does not allow node to auto join raft into ready state
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 898
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
**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
```
ha:
enabled: true
replicas: 6
raft:
enabled: true
setNodeId: true
config: |
*********OTHER_CONFIG******
storage "raft" {
path = "/vault/data"
performance_multiplier = 1
retry_join {
auto_join = "provider=k8s label_selector=\"app=vault,component=server\" namespace=\"vault\" "
leader_tls_servername = "primary-vault"
auto_join_scheme = "https"
leader_ca_cert_file = "/vault/userconfig/vault-tls/vault-ca.pem"
leader_client_cert_file = "/vault/userconfig/vault-tls/vault-cert.pem"
leader_client_key_file = "/vault/userconfig/vault-tls/vault-key.pem"
}
autopilot {
cleanup_dead_servers = "true"
last_contact_threshold = "200ms"
last_contact_failure_threshold = "10m"
max_trailing_logs = 250000
min_quorum = 6
server_stabilization_time = "10s"
}
}
```
```
k get pods
```
```
primary-vault-0 1/1 Running 0 117s
primary-vault-1 1/1 Running 0 117s
primary-vault-2 1/1 Running 0 117s
primary-vault-3 1/1 Running 0 117s
primary-vault-4 1/1 Running 0 117s
primary-vault-5 0/1 Running 0 117s
```
Other useful info to include: vault pod logs, `kubectl describe statefulset vault` and `kubectl get statefulset vault -o yaml` output
**Expected behavior**
replica of 6 + min_quorum of 6 should have 6 nodes all in ready state and joined in raft.
**Environment**
* Kubernetes version: GKE, vault-enterprise
Contributor guide
Research direction
Reproduce the Helm chart setup with replicas and min_quorum set to 6, then inspect the Vault pod logs and the StatefulSet details requested in the issue. Compare the fifth and sixth pods and the raft auto-join configuration; done means all six pods are ready and joined to raft.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, distributed-systems, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100