liveBook · Manning

Progressing condition

As explained in Kubernetes in Action, Second Edition

A progressing condition is a Deployment status condition that reports whether progress is being made toward completing an update.

A progressing condition reports whether a Deployment is making progress toward completing an update. It appears in the Deployment object's status.conditions list. section 15.2.5

If no progress occurs for 10 minutes, the condition becomes False with reason ProgressDeadlineExceeded. Set spec.progressDeadlineSeconds to use a different deadline. section 15.2.5

A failed condition reports a stalled rollout but does not stop or automatically repair it. The rollout can continue if a pod becomes ready and remains ready for minReadySeconds. section 15.2.5

Inspect a stalled rollout

Run kubectl describe deploy kiada and inspect Conditions. A stalled update can show Progressing False with reason ProgressDeadlineExceeded. kubectl rollout status deploy kiada then reports that the deployment exceeded its progress deadline.

How Kubernetes in Action, Second Edition covers it

How deep it goes
Explains status, timeout, configurable deadline, and operational consequences without detailing controller internals.
Examples
Uses kubectl describe and kubectl rollout status output to identify a stalled Deployment.
What it assumes
Assumes familiarity with Deployments, rollouts, pod readiness, and kubectl inspection commands.
What you can do after
Diagnose stalled rollouts by inspecting condition status, reason, and progress-deadline errors.
How it connects
Connects Deployment rollouts with readiness probes, minReadySeconds, and progress deadlines.

This explainer was generated by Manning's knowledge graph from the text of Kubernetes in Action, Second Edition. The section links point to the parts of the book it draws on.