Be more explicit about what kind of probe (#17943)
My guess is that this refers to a TCP probe as opposed to the HTTP probe referred to above.
This commit is contained in:
parent
093245229b
commit
ed95607ae6
|
@ -356,7 +356,7 @@ 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
|
||||
For a TCP 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.
|
||||
|
||||
|
|
Loading…
Reference in New Issue