From dbf7879dc01eed79137ee13be866a9d04eb32a23 Mon Sep 17 00:00:00 2001 From: Dan Winship Date: Tue, 19 Apr 2016 09:38:32 -0400 Subject: [PATCH] Warn that iptables proxier doesn't handle readiness failures. --- docs/user-guide/services/index.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/docs/user-guide/services/index.md b/docs/user-guide/services/index.md index 10189ddad0..232232af27 100644 --- a/docs/user-guide/services/index.md +++ b/docs/user-guide/services/index.md @@ -193,7 +193,10 @@ default is `"None"`). As with the userspace proxy, the net result is that any traffic bound for the `Service`'s IP:Port is proxied to an appropriate backend without the clients knowing anything about Kubernetes or `Services` or `Pods`. This should be -faster and more reliable than the userspace proxy. +faster and more reliable than the userspace proxy. However, unlike the +userspace proxier, the iptables proxier cannot automatically retry another +`Pod` if the one it initially selects does not respond, so it depends on +having working [readiness probes](/docs/user-guide/production-pods/#liveness-and-readiness-probes-aka-health-checks). ![Services overview diagram for iptables proxy](/images/docs/services-iptables-overview.svg)