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

Warn that iptables proxier doesn't handle readiness failures.

Browse Source
This commit is contained in:
Dan Winship
2016-04-19 09:38:32 -04:00
parent f973b70cd4
commit dbf7879dc0
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/user-guide/services/index.md
+4 -1
View File
@@ -193,7 +193,10 @@ default is `"None"`).
As with the userspace proxy, the net result is that any traffic bound for the 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 `Service`'s IP:Port is proxied to an appropriate backend without the clients
knowing anything about Kubernetes or `Services` or `Pods`. This should be 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) ![Services overview diagram for iptables proxy](/images/docs/services-iptables-overview.svg)