Kubernetes - Health Checks and Probes
Why might a Kubernetes HTTP readiness probe succeed but the pod still not serve traffic correctly?
Why might a Kubernetes HTTP readiness probe succeed but the pod still not serve traffic correctly?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Understand readiness probe scope
Readiness probe checks only the HTTP response status, not deeper app state.Step 2: Reason why traffic might fail despite probe success
The app might be partially ready or have internal errors not detected by the probe.Final Answer:
Probe only checks HTTP response, not full app readiness -> Option CQuick Check:
Readiness probe checks HTTP status, not full app health [OK]
Quick Trick: HTTP probe checks response, not full app readiness [OK]
Common Mistakes:
- Assuming probe frequency causes overload
- Confusing readiness with liveness probe status
- Thinking TCP socket probe checks HTTP readiness
Master "Health Checks and Probes" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes