5c9e36ef80
Automatic merge from submit-queue (batch tested with PRs 52768, 51898, 53510, 53097, 53058). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Run IPVS proxier UTs everywhere - include !linux platfrom **What this PR does / why we need it**: IPVS proxier UTs should run everywhere, including !linux platfrom, which will help a lot when developing in windows platfrom. **Which issue this PR fixes**: fixes #53099 **Special notes for your reviewer**: **Release note**: ```release-note NONE ``` |
||
---|---|---|
.. | ||
BUILD | ||
README.md | ||
proxier.go | ||
proxier_test.go |
README.md
How to use IPVS
This document shows how to use kube-proxy ipvs mode.
What is IPVS
IPVS (IP Virtual Server) implements transport-layer load balancing, usually called Layer 4 LAN switching, as part of Linux kernel.
IPVS runs on a host and acts as a load balancer in front of a cluster of real servers. IPVS can direct requests for TCP and UDP-based services to the real servers, and make services of real servers appear as irtual services on a single IP address.
How to use
Load IPVS kernel modules
Currently the IPVS kernel module can't be loaded automatically, so first we should use the following command to load IPVS kernel modules manually.
modprobe ip_vs
modprobe ip_vs_rr
modprobe ip_vs_wrr
modprobe ip_vs_sh
modprobe nf_conntrack_ipv4
After that, use lsmod | grep ip_vs
to make sure kernel modules are loaded.
Run kube-proxy in ipvs mode
First, run cluster locally.
By default kube-proxy will run in iptables mode, with configuration file /tmp/kube-proxy.yaml
. so we need to change the
configuration file and restart it. Here is a yaml file for reference.
apiVersion: componentconfig/v1alpha1
kind: KubeProxyConfiguration
clientConnection:
kubeconfig: /var/run/kubernetes/kube-proxy.kubeconfig
hostnameOverride: 127.0.0.1
mode: ipvs
featureGates: AllAlpha=true
ipvs:
minSyncPeriod: 10s
syncPeriod: 60s
Test
Use ipvsadm
tool to test whether the kube-proxy start succeed. By default we may get result like:
# ipvsadm -ln
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 10.0.0.1:443 rr persistent 10800
-> 10.229.43.2:6443 Masq 1 0 0
TCP 10.0.0.10:53 rr
UDP 10.0.0.10:53 rr