readiness probe
A check that decides whether a pod should receive traffic right now; failing it removes the pod from its Service without restarting it.
In more detail
It is often an HTTP request to a path such as /ready, and failing it takes the instance out of load balancing without a restart. That suits warm-up, overload, a missing dependency or draining during shutdown. Keep it separate from the liveness probe, which restarts a container that has stopped working.
Example
readinessProbe:
httpGet:
path: /
port: 8080Related terms
- rolling update — Replacing instances of an application with the new version a few at a time while the rest keep serving.
- health status — Argo CD's verdict on whether a resource works: Healthy, Progressing, Degraded, Suspended, Missing or Unknown.
- liveness probe — A health check that answers only whether a process is alive enough to keep running; if it keeps failing, the orchestrator, such as Kubernetes, restarts it.
- EndpointSlice — The object that lists the actual pod addresses behind a Service and whether each one is ready.
- health check — A regular automated test of whether a program or service is working, such as a request to its health endpoint or a command run inside its container.
- health endpoint — A web address, often /health, that a service answers quickly to show it is up.
- Kubernetes — An open-source system that runs and manages containers across a cluster of machines.
- container orchestrator — A system that decides where containers run and keeps them running, restarting, scaling and replacing them automatically.
- graceful shutdown — Stopping a service in an orderly way: finish current work, close connections, then exit.
- load balancing — Spreading requests or connections across several backend servers so no single one is overloaded and failed ones can be avoided.
- container probe — A regular check the kubelet runs against a container, such as an HTTP request or a command, to decide whether it is started, ready or alive.
- rollout — The controlled change of a Deployment, DaemonSet or StatefulSet from one pod template version to the next.
- connection draining — Stopping new traffic to a backend while letting its existing connections finish, before removing or restarting it.
- 503 Service Unavailable — The HTTP status code meaning the server cannot handle the request right now, for example because it is overloaded or shutting down.
Related guides
Taught in
- Rolling Updates and Rollbacks — Continuous Integration & Continuous Delivery Pipelines
- A Service With Nobody Behind It — Certified Kubernetes Administrator (CKA) Exam Prep
- Four Faults, Twelve Minutes — Certified Kubernetes Administrator (CKA) Exam Prep
- Self-Healing And Autoscaling: Who Restarts, Who Replaces, Who Adds — Certified Kubernetes Administrator (CKA) Exam Prep
- Running, And Still Down — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Canary Releases From Replica Counts — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Kustomize Bases, Overlays And Patches — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Probes And Health Checks — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Monitoring With The Built-in CLI — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Debugging Applications In Kubernetes — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Observability: Timed Drill And Checkpoint — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Services And Empty Endpoints — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Final Review: Where Your Marks Are At Risk — Certified Kubernetes Application Developer (CKAD) Exam Prep
- From Local Containers To Kubernetes — Docker Architecture & Production Containers
- Health Checks — Modern .NET Core, C# & Enterprise Microservices
- Health Probes & Graceful Shutdown: Kubernetes Lifecycles — Production Full-Stack Engineering
- Kubernetes Ingress, Routing & TLS Termination — Production Full-Stack Engineering
- Serving HTTP with net/http Server — Concurrent Systems Programming with Go
- One Command, Six Programs — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- A Name That Outlives Its Pods: Services And DNS — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- The Status Tells You Where To Look: Troubleshooting Pods — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Always A Way Back: Rolling, Blue/Green And Canary — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Running, Green And Still Broken: Debugging Applications — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Delivery Sprint: Friday At Five — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Slow, Or Broken? Metrics, Logs And Traces — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Architecture Sprint: The Refunds Review — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Forty Four Of Sixty: The Full Mock, And How To Read It — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- The Festival, End To End: Final Review — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- From Docker To Desired State — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: describe, Events And A First Smoke Test — Kubernetes: Production-Grade Container Orchestration
- Pods, Init Containers And Sidecars — Kubernetes: Production-Grade Container Orchestration
- Deployments, ReplicaSets, Rollouts And Rollback — Kubernetes: Production-Grade Container Orchestration
- DaemonSets And Node Services — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: Probes, Logs, exec And CrashLoopBackOff — Kubernetes: Production-Grade Container Orchestration
- ClusterIP, Selectors, EndpointSlices And DNS — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: DNS, Empty Endpoints And Broken Routes — Kubernetes: Production-Grade Container Orchestration
- Production Hardening: Graceful Shutdown & Docker — Node.js Internals & Backend Services
References
- Kubernetes: Configure liveness, readiness and startup probes
- Health checks in ASP.NET Core
- Kubernetes: Liveness, readiness and startup probes