liveness and readiness
Liveness asks whether a process should be restarted; readiness asks whether it should receive work.
Use this when Deployments send traffic too soon or restart healthy processes during dependency failures.
without the term
“When the database blips, Kubernetes restarts all our pods at once and makes it worse. And new pods get traffic before they've warmed up. How should health checks work?”
with the term · How do you ask a model for liveness and readiness?
Separate liveness and readiness for this service. Verify an unavailable dependency stops unsafe traffic without causing unnecessary process restarts.
What is liveness and readiness?
A liveness check failing means 'restart me'. A readiness check failing means 'send me no traffic for now'. Database outages belong in readiness, or every instance restarts at once.
Why does liveness and readiness matter when vibe coding?
Using one deep health check for every purpose can create restart storms.
How do you do liveness and readiness?
Define separate probes and test startup, dependency loss, and recovery.
What goes wrong with liveness and readiness?
A probe depends on the same congested path whose health it should diagnose.