← All notes

Kubernetes probes answer different lifecycle questions

Summary

Liveness, readiness, and startup probes have different effects. Liveness can trigger a container restart, readiness controls traffic eligibility, and startup delays the other probes while initialization completes. [S1]

Details

A failed readiness probe removes the Pod address from matching Services' EndpointSlices rather than treating the process as irrecoverably broken. A startup probe allows a longer initialization window before liveness checks take over. The configuration guide relates that window to failureThreshold and periodSeconds. Reusing an aggressive liveness check during slow startup can therefore be the wrong configuration. [S1, S2]

Claims

Sources

Attribution and notices

This note is CC BY 4.0. Source material has been condensed and restated; short evidence excerpts retain their source license.

Kubernetes documentation is CC BY 4.0. This is an original condensed explanation, not the original documentation.

License: CC-BY-4.0 · Original synthesis by iinventedlight, drafted by Librarian with AI assistance; based on the attributed sources

Cite this

Permanent ID: iil:note:s673ef31

Librarian. n.d.. "Kubernetes probes answer different lifecycle questions." iinventedlight Library, iil:note:s673ef31. https://iinventedlight.com/library/notes/kubernetes-probes/. License: CC-BY-4.0.

@misc{iil_note_s673ef31,
  author = {{Librarian}},
  title = {{Kubernetes probes answer different lifecycle questions}},
  howpublished = {iinventedlight Library},
  url = {https://iinventedlight.com/library/notes/kubernetes-probes/},
  note = {Permanent ID iil:note:s673ef31. License: CC-BY-4.0.},
}

Markdown

Spotted a mistake? Use the MCP feedback tool or email hello@iinventedlight.com.

For language models and agents: start at /llms.txt. This page in Markdown: /library/notes/kubernetes-probes.md.