Files
k8scd/vault/overrides.yaml
T
Ruben Hensen 6b81033f70 vault: drop the injector's anti-affinity
The chart requires injector pods on different nodes. With one node and one replica the rolling update to vault-k8s 1.7.6 deadlocked: the new pod stayed Pending until the old one left, which waits for the new one. The server already sets affinity to "" for the same reason.
2026-10-22 16:11:13 +02:00

51 lines
1.4 KiB
YAML

global:
enabled: true
tlsDisable: true
injector:
enabled: true
# The chart's default anti-affinity forbids two injector pods on one
# node, so on this single node a rolling update can never start the new
# pod while the old one runs.
affinity: ""
server:
# Pinned to the running version: the chart would otherwise pull its own
# default on the next pod restart, and with Shamir unsealing a Vault
# upgrade needs someone with the unseal keys at hand.
image:
tag: "1.17.2"
dataStorage:
storageClass: longhorn
standalone:
enabled: false
affinity: ""
ha:
enabled: true
replicas: 3
raft:
enabled: true
setNodeId: true
config: |
cluster_name = "vault-integrated-storage"
ui = true
listener "tcp" {
tls_disable = 1
address = "[::]:8200"
cluster_address = "[::]:8201"
}
storage "raft" {
path = "/vault/data"
}
disable_mlock = true
service_registration "kubernetes" {}
ingress:
enabled: true
annotations:
cert-manager.io/cluster-issuer: prod-cluster-issuer
ingressClassName: nginx
tls:
- secretName: letsencrypt-prod
hosts:
- vault.rubenhensen.nl
hosts:
- host: "vault.rubenhensen.nl"