✳flâneur — a map of the web's best reading

Kubernetes API health endpoints | Kubernetes

kubernetes.io · 651 words · saved by 1 readers

4 days of incredible opportunities to collaborate, learn + share with the entire community! November 6 - November 9, 2023. The Kubernetes API server provides API endpoints to indicate the current status of the API server. This page describes these API endpoints and explains how you can use them. The Kubernetes API server provides 3 API endpoints (healthz, livez and readyz) to indicate the current status of the API server. The healthz endpoint is deprecated (since Kubernetes v1.16), and you should use the more specific livez and readyz endpoints instead. The livez endpoint can be used with the --livez-grace-period flag to specify the startup duration. For a graceful shutdown you can specify the --shutdown-delay-duration flag with the /readyz endpoint. Machines that check the healthz/livez/readyz of the API server should rely on the HTTP status code. A status code 200 indicates the API server is healthy/live/ready, depending on the called endpoint. The more verbose options shown below ar

Kubernetes API health endpoints | Kubernetes Edit this page Create child page Create an issue Print entire section Kubernetes API health endpoints The Kubernetes API server provides API endpoints to indicate the current status of the API server. This page describes these API endpoints and explains how you can use them. API endpoints for health The Kubernetes API server provides 3 API endpoints ( healthz , livez and readyz ) to indicate the current status of the API server. The healthz endpoint is deprecated (since Kubernetes v1.16), and you should use the more specific livez and readyz endpoin

Explore this link on the map →

related reading