Search the library

Measure elapsed time locally with nanoTime and give each stage only the shared budget remaining. Expiry stops admission of more work; it does not prove a remote write was cancelled.

Use bounded connection pools, semaphores or worker queues, request deadlines, and deliberate overload responses. Local limits must account for replica count because each replica has its own pool. Avoid unbounded in-memory tasks and retries that amplify load during an incident.

Readiness is a traffic signal: if it fails, the pod is removed from service endpoints and users are not routed to it. Liveness is a health check for the process itself: if it fails, Kubernetes restarts the container. A pod can be alive but not ready, and that is often the correct state during startup or dependency warm-up.

Check whether readiness turns true before the app can serve, whether shutdown stops accepting work too early, and whether terminationGracePeriodSeconds/preStop allow endpoint withdrawal and connection draining. Also inspect maxUnavailable/maxSurge and ingress upstream errors. Correlate events, endpoint changes, and 502 timestamps before tuning a single probe.