Skip to content

Commit 491961e

Browse files
committed
fix minor typos in ipvs readme.md
1 parent 0e2220b commit 491961e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

pkg/proxy/ipvs/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ IPVS proxier will fall back on IPTABLES in the following scenarios.
6262

6363
**1. kube-proxy starts with --masquerade-all=true**
6464

65-
If kube-proxy starts with `--masquerade-all=true`, IPVS proxier will masquerade all traffic accessing service Cluster IP, which behaves the same as what IPTABLES proxier. Suppose kube-proxy have flag `--masquerade-all=true` specified, then the IPTABLES installed by IPVS proxier should be like what is shown below.
65+
If kube-proxy starts with `--masquerade-all=true`, IPVS proxier will masquerade all traffic accessing service Cluster IP, which behaves the same as what IPTABLES proxier. Suppose kube-proxy has flag `--masquerade-all=true` specified, then the IPTABLES installed by IPVS proxier should be like what is shown below.
6666

6767
```shell
6868
# iptables -t nat -nL
@@ -133,7 +133,7 @@ ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 match-set KUBE-CLU
133133
For loadBalancer type service, IPVS proxier will install IPTABLES with match of ipset `KUBE-LOAD-BALANCER`.
134134
Specially when service's `LoadBalancerSourceRanges` is specified or specified `externalTrafficPolicy=local`,
135135
IPVS proxier will create ipset sets `KUBE-LOAD-BALANCER-LOCAL`/`KUBE-LOAD-BALANCER-FW`/`KUBE-LOAD-BALANCER-SOURCE-CIDR`
136-
and install IPTABLES accordingly, which should looks like what is shown below.
136+
and install IPTABLES accordingly, which should look like what is shown below.
137137

138138
```shell
139139
# iptables -t nat -nL
@@ -184,7 +184,7 @@ ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 match-set KUBE-LOA
184184

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

189189
Suppose service with TCP type nodePort.
190190

@@ -223,7 +223,7 @@ KUBE-NODE-PORT all -- 0.0.0.0/0 0.0.0.0/0 match-set KUB
223223
**5. Service with externalIPs specified**
224224

225225
For service with `externalIPs` specified, IPVS proxier will install IPTABLES with match of ipset `KUBE-EXTERNAL-IP`,
226-
Suppose we have service with `externalIPs` specified, IPTABLES rules should looks like what is shown below.
226+
Suppose we have service with `externalIPs` specified, IPTABLES rules should look like what is shown below.
227227

228228
```shell
229229
Chain PREROUTING (policy ACCEPT)

0 commit comments

Comments
 (0)