Stalled rollouts and progressDeadlineSeconds
WHAT IT TESTS: Understanding stalled rollouts. OUTLINE: With maxUnavailable respected, the rollout pauses partway and old Pods keep serving; progressDeadlineSeconds marks the Deployment as failed after no progress for that window.
WHAT IT TESTS: Whether you know rollouts fail safe rather than crash the service. ANSWER OUTLINE: If new Pods never become Ready, the rolling update cannot satisfy its readiness gates, so it halts partway; under maxUnavailable the old ReplicaSet keeps enough healthy Pods serving traffic. progressDeadlineSeconds is the time the controller waits without progress before setting the Deployment's Progressing condition to False with reason ProgressDeadlineExceeded, signaling failure for tooling.
Read the original → interview
- #kubernetes
- #rollout
- #progressdeadlineseconds
- #deployment
- #readiness
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.