[Solved] You configured this startupProbe: startupProbe: httpGet: path: /ready port: 80 failureThreshold: 4 periodSeconds: 10 initialDelaySeconds:... What is the most likely cause? | Kubernetes

Kubernetes - Health Checks and Probes

You configured this startupProbe:

startupProbe:
  httpGet:
    path: /ready
    port: 80
  failureThreshold: 4
  periodSeconds: 10
  initialDelaySeconds: 0

But the container restarts immediately after starting. What is the most likely cause?

AinitialDelaySeconds should be set to 0 for immediate success

BThe failureThreshold is too high causing delayed restarts

CThe port 80 is incorrect for HTTP GET probes

DThe probe starts immediately but the app is not ready to respond at /ready yet

Step-by-Step Solution

Solution:

Step 1: Analyze initialDelaySeconds
Set to 0 means probe starts immediately after container start.
Step 2: Check app readiness
If app is slow to respond at /ready, probe fails repeatedly.
Step 3: Result of failures
Repeated failures cause container restart per failureThreshold.
Final Answer:
The probe starts immediately but the app is not ready to respond at /ready yet -> Option D
Quick Check:
initialDelaySeconds=0 means no wait before probing [OK]

Quick Trick: No initial delay means probe may fail if app not ready [OK]

Common Mistakes:

Master "Health Checks and Probes" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

You configured this startupProbe: