github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-04 01:40:07 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #88710 from SataQiu/ipvs-readme-20200302

Browse Source 
kube-proxy: small cleanup for ipvs readme
This commit is contained in:
Kubernetes Prow Robot 2020-03-03 12:18:22 -08:00 committed by GitHub
commit 0773f108c7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
pkg/proxy/ipvs/README.md
View File

@ -183,7 +183,7 @@ ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 match-set KUBE-LOA
**4. NodePort type service** **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`. 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-TCP/KUBE-NODE-PORT-LOCAL-UDP`
and install IPTABLES accordingly, which should looks like what is shown below. and install IPTABLES accordingly, which should looks like what is shown below.
Suppose service with TCP type nodePort. Suppose service with TCP type nodePort.
@ -323,7 +323,7 @@ export KUBE_PROXY_MODE=ipvs
### GCE Cluster ### GCE Cluster
Similar to local-up cluster, kube-proxy in [clusters running on GCE](https://kubernetes.io/docs/getting-started-guides/gce/) run in IPTABLES mode by default. Users need to export the env `KUBE_PROXY_MODE=ipvs` before [starting a cluster](https://kubernetes.io/docs/getting-started-guides/gce/#starting-a-cluster): Similar to local-up cluster, kube-proxy in [clusters running on GCE](https://kubernetes.io/docs/getting-started-guides/gce/) run in IPTABLES mode by default. Users need to export the env `KUBE_PROXY_MODE=ipvs` before [starting a cluster](https://kubernetes.io/docs/getting-started-guides/gce/#starting-a-cluster):
```shell ```shell
#before running one of the commands chosen to start a cluster: #before running one of the commands chosen to start a cluster:
# curl -sS https://get.k8s.io | bash # curl -sS https://get.k8s.io | bash
@ -369,7 +369,7 @@ Prot LocalAddress:Port Scheduler Flags
TCP 10.0.0.1:443 rr persistent 10800 TCP 10.0.0.1:443 rr persistent 10800
-> 192.168.0.1:6443 Masq 1 1 0 -> 192.168.0.1:6443 Masq 1 1 0
``` ```
or similar logs occur in kube-proxy logs (for example, `/tmp/kube-proxy.log` for local-up cluster) when the local cluster is running: or similar logs occur in kube-proxy logs (for example, `/tmp/kube-proxy.log` for local-up cluster) when the local cluster is running:
``` ```
Using ipvs Proxier. Using ipvs Proxier.
``` ```