K8s Readiness vs Liveness Probes

Question

What is the difference between readiness and liveness probes in Kubernetes?

Accepted Answer

Kubernetes probes are fundamental for ensuring application health and reliability within a cluster. While both readiness and liveness probes contribute to a robust system, they serve distinct purposes critical for different stages of a pod's lifecycle and operational health. The **readiness probe** determines if a pod is ready to serve traffic. Its primary function is to prevent traffic from being routed to a pod that is still initializing or temporarily unavailable. If a readiness probe fails, Kubernetes removes the pod's IP address from the associated Service's endpoints, effectively taking it out of rotation without restarting the container. This ensures that only healthy, fully initialized pods receive requests, preventing users from encountering errors during application startup or transient issues. The **liveness probe**, conversely, determines if a container within a pod is healthy and running as expected. If a liveness probe fails, Kubernetes assumes the container is unhealthy or deadlocked and takes corrective action by terminating the container. Following the pod's `restartPolicy`, the container is typically restarted. This mechanism is crucial for recovering from internal application deadlocks, memory leaks, or crashes that don't necessarily cause the process to exit but render the application unresponsive. Both probe types can be configured using identical mechanisms: **HTTP GET** (making an HTTP request and checking the status code), **TCP Socket** (attempting to open a TCP connection), or **Exec** (running a command inside the container and checking its exit code). Key configuration parameters include `initialDelaySeconds` (how long to wait before the first probe), `periodSeconds` (how often to perform the probe), `timeoutSeconds` (how long to wait for a response), `successThreshold` (consecutive successes needed for success), and `failureThreshold` (consecutive failures before action is taken). Effectively utilizing both readiness and liveness probes is paramount for building resilient Kubernetes applications. They work together to ensure that applications are both prepared to serve traffic and continuously operating healthily, significantly enhancing overall system stability and user experience.

K8s Readiness vs Liveness Probes

Ready to prove your Kubernetes administration knowledge?

Kubernetes Pod Stuck in Pending

Kubernetes Pod Restart Loop Troubleshooting

Investigating High CPU Usage in Kubernetes Pods

Kubernetes Pod Stuck in Pending

Node Disk Full

Kubernetes Production Readiness Checklist

Chaos Engineering for Realists: Safe Experiments You Can Run This Quarter

Cost-Aware SRE: FinOps Practices Without Sacrificing Reliability