Waylon Walker

πŸ’­ Configure Liveness, Readiness and Startup Probes | Kubernetes

Waylon Walker avatar
Author
1 min read
Copy this post
Configure Liveness, Readiness and Startup Probes β€” This page shows how to configure liveness, readiness and startup probes for containers. For more information about probes, see Liveness, Readiness and Startup Probes The kubelet uses liveness probes to know when to restart a container. For example, liveness probes could catch a deadlock, where an application is running, but unable to make progress. Restarting a container in such a state can help to make the application more available despite bugs.
Configure Liveness, Readiness and Startup Probes
This page shows how to configure liveness, readiness and startup probes for containers. For more information about probes, see Liveness, Readiness and Startup Probes The kubelet uses liveness probe...
Kubernetes Β· kubernetes.io

What is the difference between health, liveness, readiness, and startup? This article does a great job at a full writeup description of how it works in kubernetes, here is my TLDR.

  • health 200 OK - I’m still responding to requests

  • health ERR - something happened and I cant respond to requests

  • liveness 200 OK - I’m ready for more work

  • liveness ERR - I’m still responding to requests, and i’m already working send requests to another pod, or scale up

Z-pages #

These probes are commonly deployed at /healthz and /livez endpoints.

Why the z?

z is a convention that comes from google for meta endpoints to reduce conflict with actual endpoints, and can be deployed to any application.

Note

This post is a thought. It’s a short note that I make about someone else’s content online #thoughts