Loading…
A short voice session: one question, one follow-up, then instant feedback — up to 5 minutes.
Readiness controls eligibility for normal Service traffic, liveness can trigger a container restart, and startup probes protect initialization. They answer different health questions.
A startup probe delays the other probes until startup succeeds. Readiness failure normally removes eligibility for matching Service traffic; it does not itself restart the container. Liveness should detect a condition a restart can help. Making liveness fail whenever a shared dependency is unavailable can create restart storms instead of recovery.