kubernetes probes ai_generated true

Readiness probe failed: HTTP probe failed with statuscode: 503

ID: kubernetes/readiness-probe-failed

Also available as: JSON · Markdown
93%Fix Rate
95%Confidence
50Evidence
2023-01-01First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
8 active — — —
8 active — — —

Root Cause

Container's readiness probe is failing — Kubernetes won't send traffic to the pod.

generic

Workarounds

  1. 95% success Check the health endpoint inside the container: kubectl exec <pod> -- curl localhost:<port>/health 
    Verify the app is actually responding on the probed path
  2. 88% success Adjust probe timing: increase initialDelaySeconds, periodSeconds, failureThreshold 
    Slow-starting apps need longer initial delay

    Sources: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/

Dead Ends

Common approaches that don't work:

  1. Removing the readiness probe 85% fail

    All traffic goes to unready pods; users see 500 errors

  2. Setting the probe to check a path that always returns 200 80% fail

    Defeats the purpose of readiness checks

Error Chain

Frequently confused with: