Skip to content

Commit f893486

Browse files
committed
ipvs proxier README: fix typo
1 parent 2c800c5 commit f893486

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

pkg/proxy/ipvs/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Differences between IPVS mode and IPTABLES mode are as follows:
3838

3939
### When IPVS falls back to IPTABLES
4040
IPVS proxier will employ IPTABLES in doing packet filtering, SNAT or masquerade.
41-
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.
41+
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.
4242

4343

4444
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
183183
**4. NodePort type service**
184184

185185
For NodePort type service, IPVS proxier will install IPTABLES with match of ipset `KUBE-NODE-PORT-TCP/KUBE-NODE-PORT-UDP`.
186-
When specified `externalTrafficPolicy=local`,IPVS proxier will create ipset sets `KUBE-NODE-PORT-LOCAL-TC/KUBE-NODE-PORT-LOCAL-UDP`
186+
When specified `externalTrafficPolicy=local`, IPVS proxier will create ipset sets `KUBE-NODE-PORT-LOCAL-TC/KUBE-NODE-PORT-LOCAL-UDP`
187187
and install IPTABLES accordingly, which should looks like what is shown below.
188188

189189
Suppose service with TCP type nodePort.

0 commit comments

Comments
 (0)