You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a `livez` endpoint to identify network outages. This helps in
restarting the binary if such as case is observed.
Signed-off-by: Pranshu Srivastava <[email protected]>
Signed-off-by: Pranshu Srivastava <[email protected]>
Copy file name to clipboardExpand all lines: README.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -342,6 +342,14 @@ Note that your GCP identity is case sensitive but `gcloud info` as of Google Clo
342
342
343
343
After running the above, if you see `Clusterrolebinding "cluster-admin-binding" created`, then you are able to continue with the setup of this service.
344
344
345
+
#### Healthcheck Endpoints
346
+
347
+
The following healthcheck endpoints are available, some of which are used to determine the result of the aforementioned probes:
348
+
349
+
*`/livez`: Returns a 200 status code if the application is not affected by an outage of the Kubernetes API Server. We recommend to use this as a liveness probe.
350
+
*`/metrics`: Returns a 200 status code if the application is able to serve metrics. While this is available for both ports, we recommend to use the telemetry metrics endpoint as a readiness probe.
351
+
*`/healthz`: Returns a 200 status code if the application is running. We recommend to use this as a startup probe.
352
+
345
353
#### Limited privileges environment
346
354
347
355
If you want to run kube-state-metrics in an environment where you don't have cluster-reader role, you can:
Copy file name to clipboardExpand all lines: README.md.tpl
+8Lines changed: 8 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -343,6 +343,14 @@ Note that your GCP identity is case sensitive but `gcloud info` as of Google Clo
343
343
344
344
After running the above, if you see `Clusterrolebinding "cluster-admin-binding" created`, then you are able to continue with the setup of this service.
345
345
346
+
#### Healthcheck Endpoints
347
+
348
+
The following healthcheck endpoints are available, some of which are used to determine the result of the aforementioned probes:
349
+
350
+
* `/livez`: Returns a 200 status code if the application is not affected by an outage of the Kubernetes API Server. We recommend to use this as a liveness probe.
351
+
* `/metrics`: Returns a 200 status code if the application is able to serve metrics. While this is available for both ports, we recommend to use the telemetry metrics endpoint as a readiness probe.
352
+
* `/healthz`: Returns a 200 status code if the application is running. We recommend to use this as a startup probe.
353
+
346
354
#### Limited privileges environment
347
355
348
356
If you want to run kube-state-metrics in an environment where you don't have cluster-reader role, you can:
0 commit comments