---
title: Kubernetes probes answer different lifecycle questions
slug: kubernetes-probes
license: CC-BY-4.0
license_url: https://creativecommons.org/licenses/by/4.0/
source: https://iinventedlight.com/library/notes/kubernetes-probes.md
source_license: CC-BY-4.0
attribution: Original synthesis by iinventedlight, drafted by Librarian with AI assistance; based on the attributed sources
  below.
author: Librarian
client: Librarian
date: '2026-11-05'
checked_on: '2026-11-05'
as_of: '2026-11-05'
status: published
confidence: medium
category: coding-references
tags:
- kubernetes
- probes
untested: Reference note. No code or commands were run to validate behavior.
sources:
- id: S1
  title: Liveness, readiness, and startup probes
  publisher: The Kubernetes Authors
  url: https://kubernetes.io/docs/concepts/configuration/liveness-readiness-startup-probes/
  accessed: '2026-11-05'
  license: CC-BY-4.0
  license_url: https://raw.githubusercontent.com/kubernetes/website/main/LICENSE
  license_verified: '2026-11-05'
  green: true
  attribution: The Kubernetes Authors; Liveness, readiness, and startup probes; CC-BY-4.0
  snapshot: _fetched/k-probes.txt
- id: S2
  title: Configure liveness, readiness, and startup probes
  publisher: The Kubernetes Authors
  url: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/
  accessed: '2026-11-05'
  license: CC-BY-4.0
  license_url: https://raw.githubusercontent.com/kubernetes/website/main/LICENSE
  license_verified: '2026-11-05'
  green: true
  attribution: The Kubernetes Authors; Configure liveness, readiness, and startup probes; CC-BY-4.0
  snapshot: _fetched/k-configprobe.txt
---
# 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
- id: C1
  claim: "Liveness probes determine when a container needs restarting."
  source: S1
  evidence: "Liveness probes determine when to restart a container"
- id: C2
  claim: "Startup probes gate liveness and readiness checks."
  source: S1
  evidence: "until the startup probe succeeds"
- id: C3
  claim: "The startup allowance depends on failureThreshold and periodSeconds."
  source: S2
  evidence: "failureThreshold * periodSeconds long\nenough to cover the worst case startup time"

## Sources
- [S1] Liveness, readiness, and startup probes. The Kubernetes Authors. https://kubernetes.io/docs/concepts/configuration/liveness-readiness-startup-probes/. CC-BY-4.0; license: https://raw.githubusercontent.com/kubernetes/website/main/LICENSE. Accessed 2026-11-05.
- [S2] Configure liveness, readiness, and startup probes. The Kubernetes Authors. https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/. CC-BY-4.0; license: https://raw.githubusercontent.com/kubernetes/website/main/LICENSE. Accessed 2026-11-05.

## 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.