Kubernetes - Health Checks and Probes
Why does Kubernetes separate readiness and liveness probes instead of using a single probe for both?
Why does Kubernetes separate readiness and liveness probes instead of using a single probe for both?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Understand purpose of readiness probe
Readiness probe controls if container receives traffic without affecting container lifecycle.Step 2: Understand purpose of liveness probe
Liveness probe detects unhealthy containers and triggers restarts to recover them.Step 3: Reason why separation is needed
Separating probes allows Kubernetes to avoid restarting containers just because they are temporarily not ready.Final Answer:
To allow traffic control without unnecessary container restarts -> Option DQuick Check:
Separate probes = traffic control + restart control [OK]
Quick Trick: Separate probes avoid restarts when container is temporarily not ready [OK]
Common Mistakes:
- Thinking readiness probes are faster
- Assuming fewer probes reduce CPU significantly
- Believing liveness probes only use HTTP GET
Master "Health Checks and Probes" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes