TOPIC CONTAINERS
Health Checks alive isn't ready
IN 10 SECONDS
Liveness probes check if a container is running (if it fails, the system restarts it). Readiness probes check if the application is fully booted and ready to receive real requests.
GOTCHA Point liveness probes to the same endpoint as readiness. If the database lags, liveness resets the app repeatedly, turning a temporary slowdown into an outage.
HOW PROBES MONITOR APP STATUS
01 Boot phase container process starts up. Liveness passes, but readiness fails while loading cache.
02 Ready state readiness endpoint returns 200 OK. Router begins routing traffic to the container.
03 Deadlock app crashes internally. Liveness probe gets a 500 error code.
04 Restart orchestrator kills the stuck container and launches a clean replacement.
POKE IT YOURSELF
kubectl describe pod POD_NAME | grep -i probe — inspect active health checks configuration on pod
Drill this topic →
~65 sec read