[Solved] The liveness probe is defined as: livenessProbe: httpGet: path: /health port: 8080 initialDelaySeconds: 5 periodSeconds: 10 failureThreshold: 3 What is the most likely cause? | Kubernetes

Kubernetes - Health Checks and Probes

You notice your application pod keeps restarting frequently. The liveness probe is defined as:

livenessProbe:
  httpGet:
    path: /health
    port: 8080
  initialDelaySeconds: 5
  periodSeconds: 10
  failureThreshold: 3

What is the most likely cause?

AThe readiness probe is missing

BThe liveness probe is incorrectly configured with wrong port

CThe pod has insufficient CPU resources

DThe application is not responding to the /health endpoint in time

Step-by-Step Solution

Solution:

Step 1: Analyze liveness probe behavior
Liveness probe checks /health on port 8080 every 10 seconds after 5 seconds delay.
Step 2: Understand restart cause
If app does not respond correctly 3 times (failureThreshold), Kubernetes restarts pod.
Final Answer:
The application is not responding to the /health endpoint in time -> Option D
Quick Check:
Liveness failure = app not responding, causes restart [OK]

Quick Trick: Liveness failure causes restart due to no response [OK]

Common Mistakes:

Master "Health Checks and Probes" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

You notice your application pod keeps restarting frequently. The liveness probe is defined as: