From f89348619100fd2c2e6e12c391aee320bf118145 Mon Sep 17 00:00:00 2001 From: chenyaqi01 Date: Thu, 9 Jan 2020 15:11:39 +0800 Subject: [PATCH] ipvs proxier README: fix typo --- pkg/proxy/ipvs/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pkg/proxy/ipvs/README.md b/pkg/proxy/ipvs/README.md index b90147cadce..f3a66928a27 100644 --- a/pkg/proxy/ipvs/README.md +++ b/pkg/proxy/ipvs/README.md @@ -38,7 +38,7 @@ Differences between IPVS mode and IPTABLES mode are as follows: ### When IPVS falls back to IPTABLES IPVS proxier will employ IPTABLES in doing packet filtering, SNAT or masquerade. -Specifically, IPVS proxier will use ipset to store source or destination address of traffics that need DROP or do masquerade, to make sure the number of IPTABLES rules be constant, no metter how many services we have. +Specifically, IPVS proxier will use ipset to store source or destination address of traffics that need DROP or do masquerade, to make sure the number of IPTABLES rules be constant, no matter how many services we have. Here is the table of ipset sets that IPVS proxier used. @@ -183,7 +183,7 @@ ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 match-set KUBE-LOA **4. NodePort type service** For NodePort type service, IPVS proxier will install IPTABLES with match of ipset `KUBE-NODE-PORT-TCP/KUBE-NODE-PORT-UDP`. -When specified `externalTrafficPolicy=local`,IPVS proxier will create ipset sets `KUBE-NODE-PORT-LOCAL-TC/KUBE-NODE-PORT-LOCAL-UDP` +When specified `externalTrafficPolicy=local`, IPVS proxier will create ipset sets `KUBE-NODE-PORT-LOCAL-TC/KUBE-NODE-PORT-LOCAL-UDP` and install IPTABLES accordingly, which should looks like what is shown below. Suppose service with TCP type nodePort.