Kubernetes probes that don’t CrashLoop.

The #1 cause of CrashLoopBackOff is a liveness probe that fails before the app finishes starting. Set your paths and timing and get correct liveness, readiness, and startup probe YAML for your Deployment — with the startup grace that stops the loop.

The probe that kills a healthy app

It’s one of the most confusing failures in Kubernetes: the app is fine, the logs look normal, and yet the pod keeps restarting. Almost always it’s the liveness probe firing during the boot window or checking a dependency — Kubernetes reads the failure as “dead,” restarts the container, and the cycle repeats into CrashLoopBackOff. The fix is structural: a startup probe to cover the boot, a liveness probe that only reflects the process, and a readiness probe for dependencies. Get those three right and the loop simply doesn’t happen.

Probes are the orchestrator’s version of supervision — restart what’s dead, route around what’s not ready. Whether that supervision runs in Kubernetes or on a server you own, the goal is the same: keep the thing running, correctly, without human babysitting. That’s the job a control plane is built around.