From 5634a68482f86e8db6b05326572a305e6f174bcf Mon Sep 17 00:00:00 2001 From: Anthony Watherston Date: Mon, 1 Jul 2019 20:17:20 +1000 Subject: [PATCH] Update service.md (#15219) Missing word in paragraph - reading didn't make sense. --- content/en/docs/concepts/services-networking/service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/services-networking/service.md b/content/en/docs/concepts/services-networking/service.md index c46d4478a7..dc500ed817 100644 --- a/content/en/docs/concepts/services-networking/service.md +++ b/content/en/docs/concepts/services-networking/service.md @@ -243,7 +243,7 @@ select a backend Pod. By default, kube-proxy in iptables mode chooses a backend at random. Using iptables to handle traffic has a lower system overhead, because traffic -is handled by Linux netfilter without the need switch between userspace and the +is handled by Linux netfilter without the need to switch between userspace and the kernel space. This approach is also likely to be more reliable. If kube-proxy is running in iptables mode and the first Pod that's selected