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

ops(prop): zero-downtime rolling update with single replica

Browse source 
maxUnavailable: 1 was killing the only pod before the new one was
ready, taking the site down for the entire image pull + boot window
on every deploy. Switch to maxSurge: 1 / maxUnavailable: 0 so K8s
spins up the replacement and waits for its readinessProbe to pass
before tearing down the old pod.
This commit is contained in:
Graham McIntire 2026-04-29 13:50:14 -05:00
parent 2de1b89efc
commit b66024e0c3
No known key found for this signature in database
GPG key ID: F4ABF488E6029E59
1 changed files with 8 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
k8s/deployment.yaml
View file

@ -4,15 +4,20 @@ metadata:
name: prop name: prop
namespace: prop namespace: prop
spec: spec:
# replicas is owned by the HPA in hpa.yaml (min 2 / max 5). # replicas is owned by the HPA in hpa.yaml (currently pinned at 1).
# Leaving it out here so Flux's periodic reconcile doesn't overwrite # Leaving it out here so the GitOps reconciler doesn't overwrite
# whatever replica count the autoscaler has settled on. # whatever replica count the autoscaler has settled on.
minReadySeconds: 5 minReadySeconds: 5
strategy: strategy:
type: RollingUpdate type: RollingUpdate
rollingUpdate: rollingUpdate:
# Zero-downtime rollout with a single replica: surge to 2 first,
# wait for the new pod to pass its readinessProbe, THEN tear down
# the old one. maxUnavailable: 1 (the K8s default) was killing the
# only pod before the replacement was ready, taking the site down
# for the entire image pull + boot window on every deploy.
maxSurge: 1 maxSurge: 1
maxUnavailable: 1 maxUnavailable: 0
selector: selector:
matchLabels: matchLabels:
app: prop app: prop