Bird
0
0

After deploying a pod with a liveness probe, the pod restarts repeatedly right after startup. What is the most probable cause?

medium📝 Troubleshoot Q6 of 15
Kubernetes - Production Best Practices
After deploying a pod with a liveness probe, the pod restarts repeatedly right after startup. What is the most probable cause?
AThe liveness probe is failing because the application is not ready yet
BThe pod has insufficient CPU resources
CThe pod's image is corrupted
DThe readiness probe is misconfigured
Step-by-Step Solution
Solution:
  1. Step 1: Analyze pod restart cause

    Repeated restarts often indicate the liveness probe fails and triggers pod restarts.
  2. Step 2: Consider startup timing

    If the app takes time to start, the liveness probe may fail before the app is ready.
  3. Final Answer:

    The liveness probe is failing because the application is not ready yet -> Option A
  4. Quick Check:

    Check initialDelaySeconds in liveness probe [OK]
Quick Trick: Liveness probe failing early causes pod restarts [OK]
Common Mistakes:
  • Assuming resource limits cause immediate restarts
  • Confusing readiness probe issues with liveness probe failures
  • Ignoring probe timing configurations

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes