Kubernetes Health Checks: Liveness, Readiness, and Startup Probes
When running applications on Kubernetes, knowing whether a container is actually healthy is just as important as deploying it.
This is where Kubernetes health probes become useful.
Liveness Probe
A liveness probe helps Kubernetes determine whether a container is still running correctly.
If the application becomes unhealthy and fails the liveness check repeatedly, Kubernetes can restart the container.
Readiness Probe
A readiness probe answers a different question:
"Is this application ready to receive traffic?"
A container may be running but still initializing, connecting to a database, or temporarily unable to serve requests.
When a readiness probe fails, Kubernetes can stop sending traffic to that Pod without restarting it.
Startup Probe
Startup probes are useful for applications that take a long time to start.
They give the application enough time to initialize before Kubernetes starts applying the normal liveness and readiness checks.
Why This Matters for Blue-Green Deployments
Health probes become especially important during deployments.
For example:
Blue → Current production
Green → New version
Before switching traffic to Green, Kubernetes can use readiness and liveness checks to help verify that the new Pods are actually healthy.
If Green isn't ready, traffic should remain with Blue.
AWS Connection
When running Kubernetes on Amazon EKS, these Kubernetes health checks can work alongside AWS load-balancing and monitoring services to create more reliable deployments.
For me, this was an important lesson:
Running a container doesn't necessarily mean the application is healthy.
Good deployments need health checks, monitoring, and a safe strategy for handling failures.
I'm continuing to explore Kubernetes, Amazon EKS, CI/CD, and cloud-native deployment strategies.
Loading article