[Solved] Consider this startupProbe configuration: startupProbe: exec: command: ["test", "-f", "/tmp/ready"] failureThreshold: 5 periodSeconds:... | Kubernetes

Kubernetes - Health Checks and Probes

Consider this startupProbe configuration:

startupProbe:
  exec:
    command: ["test", "-f", "/tmp/ready"]
  failureThreshold: 5
  periodSeconds: 3

What happens if the file /tmp/ready does not exist during startup?

AThe container will restart immediately without waiting

BThe probe will succeed immediately and the container continues running

CThe container will never restart because startupProbe ignores failures

DThe container will be restarted after 15 seconds of probe failures

Step-by-Step Solution

Solution:

Step 1: Calculate failure timeout
failureThreshold (5) * periodSeconds (3) = 15 seconds before restart.
Step 2: Understand exec command
The command checks for file existence; if missing, probe fails.
Step 3: Effect of repeated failures
After 5 consecutive failures, Kubernetes restarts the container.
Final Answer:
The container will be restarted after 15 seconds of probe failures -> Option D
Quick Check:
FailureThreshold x periodSeconds = restart delay [OK]

Quick Trick: FailureThreshold x periodSeconds = restart delay [OK]

Common Mistakes:

Master "Health Checks and Probes" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

More Kubernetes Quizzes

Consider this startupProbe configuration: