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

Add comment about where to run probe (#13815)

Browse Source 
* Add comment about where to run probe

Add comment about where to run probe

Signed-off-by: Xiang Dai <764524258@qq.com>

* Update language

Signed-off-by: Xiang Dai <764524258@qq.com>

* Update language

Signed-off-by: Xiang Dai <764524258@qq.com>

* Update language

Signed-off-by: Xiang Dai <764524258@qq.com>

* fix grammar nits

Signed-off-by: Xiang Dai <764524258@qq.com>
This commit is contained in:
Xiang Dai
2019-06-11 10:34:15 +08:00
committed by Kubernetes Prow Robot
parent a905be0ceb
commit d865cc456e
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md
+4
View File
@@ -310,6 +310,10 @@ 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 a probe, the kubelet makes the probe connection at the node, not in the pod, which
means that you can not use a service name in the `host` parameter since the kubelet is unable
to resolve it.
{{% /capture %}} {{% /capture %}}
{{% capture whatsnext %}} {{% capture whatsnext %}}