Write Probes That Match the Failure
Design Kubernetes startup, readiness, and liveness probes for a service with slow warm-up and dependency risk.
before-after common-trap stepper The search API warms a cache for 90 seconds, needs an index connection before serving traffic, and occasionally deadlocks under load. Separate startup, readiness, and liveness by failure mode The common trap is one /health endpoint that checks every dependency and is wired to every probe. That causes restarts during normal warm-up and traffic during partial readiness. Before One /health endpoint checks process, database, index, and cache. Kubernetes uses it for startup, readiness, and liveness. After /startup covers warm-up, /ready checks traffic-serving dependencies, and /live checks whether the process is recoverably stuck. Step 1 List the failure…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in