From d865cc456ec98484ebd152900886382e9187a793 Mon Sep 17 00:00:00 2001
From: Xiang Dai <764524258@qq.com>
Date: Tue, 11 Jun 2019 10:34:15 +0800
Subject: [PATCH] Add comment about where to run probe (#13815)

* 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>
---
 .../configure-liveness-readiness-probes.md                    | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md
index f2ba952f7b..75c3358993 100644
--- a/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md
+++ b/content/en/docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md
@@ -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
 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 whatsnext %}}