Kubernetes - Health Checks and Probes
A container's liveness probe uses HTTP GET on /status but the container never restarts even when the endpoint returns 500 errors. What is the most probable misconfiguration?
A container's liveness probe uses HTTP GET on /status but the container never restarts even when the endpoint returns 500 errors. What is the most probable misconfiguration?
medium📝 Troubleshoot Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Understand HTTP probe success criteria
By default, HTTP status codes 200-399 are success; 500 is failure and should increment failure count toward restart.Step 2: Identify misconfiguration
If the container never restarts despite repeated 500s, the failureThreshold is most likely set too high, preventing it from reaching the restart threshold.Final Answer:
The probe's failureThreshold is too high -> Option AQuick Check:
failureThreshold determines consecutive failures before restart [OK]
Quick Trick: High failureThreshold prevents quick restarts on probe failures [OK]
Common Mistakes:
- Overlooking a high failureThreshold value
- Misconfiguring probe path/port to not hit the endpoint
- Confusing successThreshold (for recovery) with failureThreshold
Master "Health Checks and Probes" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes