committed by
Kubernetes Prow Robot
parent
1b9af9ad50
commit
43021880be
@@ -253,7 +253,7 @@ Pod had failed and would automatically retry with a different backend Pod.
|
|||||||
|
|
||||||
You can use Pod [readiness probes](/docs/concepts/workloads/pods/pod-lifecycle/#container-probes)
|
You can use Pod [readiness probes](/docs/concepts/workloads/pods/pod-lifecycle/#container-probes)
|
||||||
to verify that backend Pods are working OK, so that kube-proxy in iptables mode
|
to verify that backend Pods are working OK, so that kube-proxy in iptables mode
|
||||||
only sees backends that test out as healthy. Doing this means means you avoid
|
only sees backends that test out as healthy. Doing this means you avoid
|
||||||
having traffic sent via kube-proxy to a Pod that's known to have failed.
|
having traffic sent via kube-proxy to a Pod that's known to have failed.
|
||||||
|
|
||||||

|

|
||||||
|
|||||||
Reference in New Issue
Block a user