Sign up

Kubernetes pod stuck in CrashLoopBackOff

asked 2 months ago136 viewsen

3

My deployment shows CrashLoopBackOff. kubectl logs shows the app starting then stopping. How do I debug liveness/readiness probes and startup timing?

AI diagnosis

AI-generated. Not an answer — the community below confirms or corrects it. Always verify before relying on it.

dockerkubernetes
asked 2 months ago

  • Thanks, this helped. Did you also try clearing the cache?

     — davidcharles 2 months ago

1 Answer

5
✓
✓ Accepted answer

CrashLoopBackOff almost always means the container's main process exits. Check kubectl logs --previous. Common causes: readiness probe on a port the app binds late, missing env/secret, or the app needing a writable volume it doesn't have.

Sign in to tell others whether this worked.

answered 2 months ago

Sign in and verify your email to post an answer.