mirror of
https://github.com/rubenhensen/k8scd.git
synced 2026-11-17 06:29:09 +01:00
vault: recreate the injector instead of rolling it
Dropping the anti-affinity wasn't enough: during the rollout the old ReplicaSet kept recreating its pod with the old anti-affinity, which still blocked the new one. Recreate stops the old pod first; nothing uses the injector, so the short gap doesn't matter.
This commit is contained in:
1 parent
6b81033f70
commit
b86942077a
1 file changed
+5
-1
@@ -5,8 +5,12 @@ injector:
|
|||||||
enabled: true
|
enabled: true
|
||||||
# The chart's default anti-affinity forbids two injector pods on one
|
# 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
|
# node, so on this single node a rolling update can never start the new
|
||||||
# pod while the old one runs.
|
# pod while the old one runs. Recreate removes the old pod first, which
|
||||||
|
# also gets past pods that still carry the old anti-affinity.
|
||||||
affinity: ""
|
affinity: ""
|
||||||
|
strategy:
|
||||||
|
type: Recreate
|
||||||
|
rollingUpdate: null
|
||||||
server:
|
server:
|
||||||
# Pinned to the running version: the chart would otherwise pull its own
|
# Pinned to the running version: the chart would otherwise pull its own
|
||||||
# default on the next pod restart, and with Shamir unsealing a Vault
|
# default on the next pod restart, and with Shamir unsealing a Vault
|
||||||
|
|||||||
Reference in new issue
Block a user