Tuning maxSurge and maxUnavailable
WHAT IT TESTS: Rollout strategy tuning. OUTLINE: maxSurge allows Pods above desired; maxUnavailable allows Pods below desired during update. For zero downtime and speed, set maxUnavailable 0 and maxSurge high (e.g. 100%).
WHAT IT TESTS: Whether you can balance availability against rollout speed. ANSWER OUTLINE: maxSurge is how many Pods above the desired replica count may exist temporarily; maxUnavailable is how many below desired may be down at once. Both accept absolute numbers or percentages. For zero downtime you must keep maxUnavailable at 0 so full capacity is always served. For fastest rollout you raise maxSurge so many new Pods spin up in parallel.
Read the original → interview
- #kubernetes
- #rolling-update
- #maxsurge
- #maxunavailable
- #zero-downtime
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.