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
Copy file name to clipboardExpand all lines: content/en/docs/reference/using-api/health-checks.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,6 +31,12 @@ This can be useful for a human operator to debug the current status of the Api s
31
31
curl -k https://localhost:6443/livez?verbose
32
32
```
33
33
34
+
or from a remote host with authentication:
35
+
36
+
```shell
37
+
kubectl get --raw='/readyz?verbose'
38
+
```
39
+
34
40
The output will look like this:
35
41
36
42
[+]ping ok
@@ -83,6 +89,10 @@ The output show that the `etcd` check is excluded:
83
89
[+]shutdown ok
84
90
healthz check passed
85
91
92
+
## Individual health checks
93
+
94
+
{{< feature-state state="alpha" >}}
95
+
86
96
Each individual health check exposes an http endpoint and could can be checked individually.
87
97
The schema for the individual health checks is `/livez/<healthcheck-name>` where `livez` and `readyz` and be used to indicate if you want to check thee liveness or the readiness of the API server.
88
98
The `<healthcheck-name>` path can be discovered using the `verbose` flag from above and take the path between `[+]` and `ok`.
0 commit comments