File tree Expand file tree Collapse file tree 1 file changed +12
-12
lines changed
content/en/docs/reference/using-api Expand file tree Collapse file tree 1 file changed +12
-12
lines changed Original file line number Diff line number Diff line change @@ -27,15 +27,15 @@ The following examples will show how you can interact with the health API endpoi
27
27
For all endpoints you can use the ` verbose ` parameter to print out the checks and their status.
28
28
This can be useful for a human operator to debug the current status of the Api server, it is not intended to be consumed by a machine:
29
29
30
- ```shell
31
- curl -k https://localhost:6443/livez?verbose
32
- ```
30
+ ``` shell
31
+ curl -k https://localhost:6443/livez? verbose
32
+ ```
33
33
34
34
or from a remote host with authentication:
35
35
36
- ```shell
37
- kubectl get --raw='/readyz?verbose'
38
- ```
36
+ ``` shell
37
+ kubectl get --raw=' /readyz?verbose'
38
+ ```
39
39
40
40
The output will look like this:
41
41
@@ -62,9 +62,9 @@ The output will look like this:
62
62
The Kubernetes API server also supports to exclude specific checks.
63
63
The query parameters can also be combined like in this example:
64
64
65
- ```shell
66
- curl -k 'https://localhost:6443/readyz?verbose&exclude=etcd'
67
- ```
65
+ ``` shell
66
+ curl -k ' https://localhost:6443/readyz?verbose&exclude=etcd'
67
+ ```
68
68
69
69
The output show that the ` etcd ` check is excluded:
70
70
@@ -98,6 +98,6 @@ The schema for the individual health checks is `/livez/<healthcheck-name>` where
98
98
The ` <healthcheck-name> ` path can be discovered using the ` verbose ` flag from above and take the path between ` [+] ` and ` ok ` .
99
99
These individual health checks should not be consumed by machines but can be helpful for a human operator to debug a system:
100
100
101
- ```shell
102
- curl -k https://localhost:6443/livez/etcd
103
- ```
101
+ ``` shell
102
+ curl -k https://localhost:6443/livez/etcd
103
+ ```
You can’t perform that action at this time.
0 commit comments