From d1d65e340d27a7d824d0c31ccf54c48bcfbee6f1 Mon Sep 17 00:00:00 2001 From: alainvanhoof Date: Thu, 28 Dec 2017 22:04:21 +0100 Subject: [PATCH] Update service.md (#6746) --- docs/concepts/services-networking/service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/services-networking/service.md b/docs/concepts/services-networking/service.md index ddbca9c9a0..93084f2109 100644 --- a/docs/concepts/services-networking/service.md +++ b/docs/concepts/services-networking/service.md @@ -199,7 +199,7 @@ consistent with the expectation. When access the `service`, traffic will be redirect to one of the backend `pod`. Similar to iptables, Ipvs is based on netfilter hook function, but use hash -table as the underlying data structure and work in the kernal state. +table as the underlying data structure and work in the kernel space. That means ipvs redirects traffic can be much faster, and have much better performance when sync proxy rules. Furthermore, ipvs provides more options for load balancing algorithm, such as: