whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

HTTP Probe - Update documentation about default headers

Browse Source
This commit is contained in:
Hugo Fonseca
2020-11-12 15:47:40 +00:00
parent 20546141c0
commit 2300a3e0fe
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes.md
+3 -3
View File
@@ -381,9 +381,9 @@ and the Pod's `hostNetwork` field is true. Then `host`, under `httpGet`, should
to 127.0.0.1. If your pod relies on virtual hosts, which is probably the more common to 127.0.0.1. If your pod relies on virtual hosts, which is probably the more common
case, you should not use `host`, but rather set the `Host` header in `httpHeaders`. case, you should not use `host`, but rather set the `Host` header in `httpHeaders`.
For an HTTP probe, the kubelet sends three request headers in addition to the mandatory `Host` header: For an HTTP probe, the kubelet sends two request headers in addition to the mandatory `Host` header:
`User-Agent`, `Accept-Encoding` and `Accept`. The default values for these headers are `kube-probe/{{< skew latestVersion >}}` `User-Agent`, and `Accept`. The default values for these headers are `kube-probe/{{< skew latestVersion >}}`
(where `{{< skew latestVersion >}}` is the version of the kubelet ), `gzip` and `*/*` respectively. (where `{{< skew latestVersion >}}` is the version of the kubelet ), and `*/*` respectively.
You can override the default headers by defining `.httpHeaders` for the probe; for example You can override the default headers by defining `.httpHeaders` for the probe; for example