A Deployment update stops making progress and the status later shows ProgressDeadlineExceeded. Which field primarily defines how long Kubernetes waits before marking that timeout?
Select an answer to reveal the explanation.
Short Explanation
There’s a shot clock on the rollout—if nothing useful happens before it buzzes, the play is dead. progressDeadlineSeconds is that shot clock; when it expires you get ProgressDeadlineExceeded.
Full Explanation
progressDeadlineSeconds sets how long a Deployment may make no progress before the controller surfaces ProgressDeadlineExceeded in conditions. Operators use that signal to detect stuck rollouts (bad images, scheduling failures, failing readiness). terminationGracePeriodSeconds, Job activeDeadlineSeconds, and revisionHistoryLimit address shutdown grace, Job runtime limits, and retained ReplicaSets—not rollout progress timeout.