Startup, Readiness and Liveness

Kubernetes gives you three distinct probe types, and mixing up their purposes is one of the most common causes of self-inflicted outages, so it is worth being precise about what each one is actually for. A startup probe exists purely to protect slow-initializing applications: while it is failing, Kubernetes holds off on running readiness and liveness checks at all, giving a genuinely slow boot process room to finish without being killed prematurely. Readiness answers one narrow question - can this specific instance accept traffic right now? - and failing it only removes the Pod from a Service's endpoints (as covered in the networking module); it does not restart anything. Liveness answers a different question - has this process become so broken that killing and restarting it is the only way to recover? - and failing it does trigger an actual container restart. The four timing fields (initialDelaySeconds, periodSeconds, timeoutSeconds, failureThreshold) together define a detection budget - roughly, how long a real problem can persist before Kubernetes reacts to it - and setting an aggressive liveness probe can backfire badly: if it checks something that can be slow for reasons entirely outside the application's own control (like a downstream dependency), a brief dependency slowdown gets translated into unnecessary container restarts, which is strictly worse than doing nothing. As a strong general rule, keep liveness checks narrowly local ("is my own process's event loop responsive") and conservative, and let readiness - not liveness - be where dependency health is reflected.

Analogy: Kubernetes is a thermostat, not a remote control. You declare the temperature; independent controllers measure reality and keep acting. Debugging means finding which sensor, rule or actuator prevents convergence.

Read the object as evidence

kubectl get RESOURCE NAME -n NAMESPACE -o yaml
kubectl describe RESOURCE NAME -n NAMESPACE
kubectl get events -n NAMESPACE --sort-by=.metadata.creationTimestamp
kubectl explain RESOURCE.spec

Do not memorize these as a ritual. The first command exposes desired and observed state, the second connects conditions and events, the third supplies a timeline, and the fourth checks the server's schema. Compare what the controller was asked to do with what it reports doing. Then test the narrowest hypothesis.

Scenario: A liveness probe is configured to check that the application's database connection is healthy - a well-intentioned attempt to catch a genuinely broken process. When the database itself has an unrelated outage, every single API replica's liveness probe now fails simultaneously, and Kubernetes restarts all of them at once, adding a fresh wave of reconnection load right as the database is already struggling, and destroying the in-memory diagnostic state (like recent error counters) that would have helped debug the actual outage. Dependency failures like this almost always belong in readiness (temporarily stop sending this instance new traffic) or in the application's own retry/circuit-breaker logic - not in liveness, which should be reserved for detecting that this specific process itself is unrecoverably stuck.

Budget probe timing

Compute worst-case detection from initialDelaySeconds, periodSeconds, timeoutSeconds and failureThreshold. Startup probes suppress readiness and liveness until slow initialization succeeds. Readiness should answer whether this instance can accept traffic now; liveness should answer whether restarting this process can repair it. Keep external dependencies out of liveness in most designs.

Scenario: A ten-second liveness timeout meets a fifteen-second stop-the-world pause under load. Every replica restarts in sync, increasing load and causing another pause. Conservative thresholds and jittered workload behavior prevent probe amplification.
Tip: Expose separate startup, readiness and liveness endpoints with different semantics, and monitor probe failures as an early warning rather than waiting for restarts.

Production reasoning

Ask four questions: Who owns this object? What dependency must become ready next? Which controller reports the blocking condition? What evidence would disprove my current theory? This prevents symptom-driven changes. Record the context, namespace, object generation, image digest and recent rollout before mutation; a recreated Pod may erase the evidence you needed.

Warning: Running is not the same as ready, healthy, durable or correct. Kubernetes status is layered. Confirm the application-level outcome as well as the object state.
Goal: Put this model into practice in the Kubernetes lab probe-storefront. Open /labs/kubernetes, choose probe-storefront, predict the failure path before changing anything, then use the simulator's check command to validate the finished state.

Deliberate practice

Before the lab, write the expected object relationship and the first three commands you will run. Afterward, explain why the fix converged and name one tempting change that would only mask the symptom. Repeat using an explicit namespace and a structured output format. This prediction-observation-explanation loop is what turns command familiarity into production judgment.

45-minute investigation

  1. Map (5 min): draw the owner-to-child chain and mark every namespace, selector, identity and dependency involved.
  2. Predict (5 min): write one expected status condition, one likely event and one log or metric signal before opening the lab.
  3. Observe (10 min): collect YAML, describe output and ordered events. Do not mutate state. Record which observation disproves your first theory.
  4. Repair (15 min): make the smallest declarative correction, watch the responsible controller converge, and verify the user-facing path rather than stopping at Running.
  5. Stress (10 min): change one relevant constraint - replica count, label, readiness, resource value or placement rule - predict the outcome, observe it, then restore the known-good declaration.
Tip: Keep a short incident note with symptom, evidence, hypothesis, change, result. Across four sections this produces a reusable runbook instead of a pile of remembered commands.