Microservices - Orchestration with Kubernetes
A readiness probe uses an exec command that always returns exit code 0, but the service is not ready. What is the problem?
A readiness probe uses an exec command that always returns exit code 0, but the service is not ready. What is the problem?
medium📝 Analysis Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Understand exec probe success criteria
Exec probe success depends on exit code 0; always returning 0 means probe always passes.Step 2: Consequence of always passing probe
Probe reports ready even if service is not ready, causing traffic routing issues.Final Answer:
Probe incorrectly reports ready because exit code 0 means success -> Option BQuick Check:
Exec probe exit code 0 = success, may mask readiness issues [OK]
Quick Trick: Exec probe exit code 0 means success, verify command logic [OK]
Common Mistakes:
MISTAKES- Assuming pod restarts on readiness failure
- Thinking exec command syntax causes failure
- Believing readiness probe can be ignored
Master "Orchestration with Kubernetes" in Microservices
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Microservices Quizzes