Liveness vs readiness probes
WHAT IT TESTS: Understanding probe semantics. OUTLINE: Liveness restarts a stuck container; readiness gates traffic by controlling Service endpoint membership. Readiness-only fits an app that pauses to reload a large cache but is still healthy.
WHAT IT TESTS: Whether you know the distinct lifecycle effects of each probe. ANSWER OUTLINE: A liveness probe detects a deadlocked or hung container and triggers a restart. A readiness probe decides whether a Pod should receive traffic by adding or removing it from the Service's endpoints; failing readiness does not restart the container. Readiness-but-not-liveness suits an app that periodically becomes temporarily unable to serve (warming a cache, reloading config) but is otherwise healthy and should not be killed.
Read the original → interview
- #kubernetes
- #liveness-probe
- #readiness-probe
- #pod-lifecycle
- #health-checks
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.