graham/towerops
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

ops: tighten readiness gate to prevent downtime during rolling deploys

Browse source 
With 1 replica, the old pod was torn down too quickly after the new pod
passed its first health check. Increase successThreshold to 3 (15s of
consecutive checks) and minReadySeconds to 30 to ensure Traefik has fully
propagated the new endpoint before the old pod is terminated.
This commit is contained in:
Graham McIntire 2026-04-29 13:49:42 -05:00
parent df1d361249
commit 95babfcc49
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
k8s/deployment.yaml
View file

@ -10,7 +10,7 @@ spec:
rollingUpdate: rollingUpdate:
maxSurge: 1 # Allow 3rd pod during rollout to avoid downtime maxSurge: 1 # Allow 3rd pod during rollout to avoid downtime
maxUnavailable: 0 # Keep all pods running during rollout maxUnavailable: 0 # Keep all pods running during rollout
minReadySeconds: 10 # Wait 10s after pod is ready before considering it available minReadySeconds: 30 # Wait 30s after pod is ready before considering it available (endpoint propagation buffer)
selector: selector:
matchLabels: matchLabels:
app: towerops app: towerops
@ -230,5 +230,5 @@ spec:
initialDelaySeconds: 5 initialDelaySeconds: 5
periodSeconds: 5 periodSeconds: 5
timeoutSeconds: 2 timeoutSeconds: 2
successThreshold: 1 # Mark ready after first successful check successThreshold: 3 # Require 3 consecutive successes (15s) before marking ready
failureThreshold: 2 # Allow 1 failure before marking not ready failureThreshold: 2 # Allow 1 failure before marking not ready