Bird
0
0

A pod's readiness probe is configured but the pod never transitions to Ready state. What is a likely cause?

medium📝 Troubleshoot Q7 of 15
Kubernetes - Health Checks and Probes
A pod's readiness probe is configured but the pod never transitions to Ready state. What is a likely cause?
AThe readiness probe command or HTTP path is incorrect or always failing
BThe pod's resource limits are too high
CThe liveness probe is missing
DThe pod is scheduled on a node with insufficient CPU
Step-by-Step Solution
Solution:

  1. Step 1: Check readiness probe configuration

    If the probe command or HTTP path is wrong, it will always fail.

  2. Step 2: Effect on pod state

    Pod remains Not Ready because readiness probe never succeeds.

  3. Final Answer:

    The readiness probe command or HTTP path is incorrect or always failing -> Option A

  4. Quick Check:

    Incorrect readiness probe causes pod to stay Not Ready [OK]
Quick Trick: Bad readiness probe config keeps pod Not Ready [OK]
Common Mistakes:
  • Blaming resource limits for readiness issues
  • Confusing readiness with liveness probe absence
  • Assuming node CPU affects readiness directly

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
ConfigMaps - Immutable ConfigMaps - Quiz 13medium Health Checks and Probes - Exec probe configuration - Quiz 5medium Health Checks and Probes - Startup probe concept - Quiz 10hard Health Checks and Probes - Startup probe concept - Quiz 11easy Networking - Pod-to-Pod communication - Quiz 11easy Networking - DNS in Kubernetes (CoreDNS) - Quiz 3easy Persistent Storage - Storage classes for dynamic provisioning - Quiz 11easy Persistent Storage - Reclaim policies (Retain, Delete) - Quiz 9hard Secrets - Using Secrets as environment variables - Quiz 6medium Secrets - Why Secrets manage sensitive data - Quiz 4medium