[Solved] Examine this readiness probe configuration: readinessProbe: exec: command: ["/bin/check_ready.sh"] initialDelaySeconds: 5 periodSeconds: 10 failureThreshold: 2 successThreshold: 1 timeoutSeconds:... | Kubernetes

Kubernetes - Health Checks and Probes

Examine this readiness probe configuration:

readinessProbe:
  exec:
    command: ["/bin/check_ready.sh"]
  initialDelaySeconds: 5
  periodSeconds: 10
  failureThreshold: 2
  successThreshold: 1
  timeoutSeconds: 1

What is a likely cause if Kubernetes never marks the pod as ready?

AThe script /bin/check_ready.sh is missing or not executable inside the container

BinitialDelaySeconds is too low causing premature checks

CfailureThreshold is set too low, causing immediate failure

DtimeoutSeconds is too high, delaying readiness detection

Step-by-Step Solution

Solution:

Step 1: Understand exec readiness probe
Exec probes run a command inside the container; it must exist and be executable.
Step 2: Analyze symptoms
If pod never becomes ready, the command likely fails or is missing.
Step 3: Evaluate other parameters
initialDelaySeconds, failureThreshold, and timeoutSeconds are reasonable and unlikely to cause permanent failure alone.
Final Answer:
Option A -> Option A
Quick Check:
Exec probe command must exist and be executable [OK]

Quick Trick: Exec probe fails if command missing or not executable [OK]

Common Mistakes:

Ignoring command existence inside container
Misconfiguring timing parameters
Confusing failureThreshold with successThreshold

Master "Health Checks and Probes" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More Kubernetes Quizzes

Examine this readiness probe configuration:

Step 1: Understand exec readiness probe

Step 2: Analyze symptoms

Step 3: Evaluate other parameters

Final Answer:

Quick Check:

Want More Practice?