How do readiness, liveness, and startup probes serve different purposes in Kubernetes?
Interactive Practice Mode
Formulate your thoughts or take notes before revealing the model solution.
Saved automatically
Model Answer & Deep-Dive Explanation
Readiness indicates whether a container should receive traffic through the relevant service routing. Liveness determines whether a running container should be restarted after repeated failures. A startup probe allows a slow-starting container to initialize before liveness and readiness probing begins. Configure thresholds according to observed startup and recovery behavior. A liveness probe that fails whenever a remote database is unavailable can cause a restart storm without repairing the database. Keep probes lightweight and make readiness reflect whether the instance can safely handle the traffic it will receive.
Related Questions in Cloud & DevOps Engineering
How do IaaS, PaaS, and SaaS divide operational responsibility?
Easy level • 1 views
How is a container different from a virtual machine?
Easy level • 1 views
What does infrastructure as code provide beyond a script that creates servers?
Medium level • 1 views
How would you perform a canary release and decide whether to continue or roll back?
Medium level • 1 views
What checks belong in a useful CI pipeline for a web service?
Medium level • 1 views