kube-proxy [page]deterministic
##
The Kubernetes network proxy runs on each node. This reflects services as defined in the Kubernetes API on each node and can do simple TCP, UDP, and SCTP stream forwarding or round robin TCP, UDP, and SCTP forwarding across a set of backends. Service cluster IPs and ports are currently found through Docker-links-compatible environment variables specifying ports opened by the service proxy. There is an optional addon that provides cluster DNS for these cluster IPs. The user must create a service with the apiserver API to configure the proxy.
``` kube-proxy [flags] ```
##
<table style="width: 100%; table-layout: fixed;"> <colgroup> <col span="1" style="width: 10px;" /> <col span="1" /> </colgroup> <tbody>
<tr> <td colspan="2">--add_dir_header</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>If true, adds the file directory to the header of the log messages</p></td> </tr>
<tr> <td colspan="2">--alsologtostderr</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>log to standard error as well as files (no effect when -logtostderr=true)</p></td> </tr>
<tr> <td colspan="2">--alsologtostderrthreshold int</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>logs at or above this threshold go to stderr when -alsologtostderr=true (no effect when -logtostderr=true)</p></td> </tr>
<tr> <td colspan="2">--bind-address string Default: 0.0.0.0</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Overrides kube-proxy's idea of what its node's primary IP is. Note that the name is a historical artifact, and kube-proxy does not actually bind any sockets to this IP. This parameter is ignored if a config file is specified by --config.</p></td> </tr>
<tr> <td colspan="2">--bind-address-hard-fail</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>If true kube-proxy will treat failure to bind to a port as fatal and exit</p></td> </tr>
<tr> <td colspan="2">--cleanup</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>If true cleanup iptables and ipvs rules and exit.</p></td> </tr>
<tr> <td colspan="2">--cluster-cidr string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>The CIDR range of the pods in the cluster. (For dual-stack clusters, this can be a comma-separated dual-stack pair of CIDR ranges.). When --detect-local-mode is set to ClusterCIDR, kube-proxy will consider traffic to be local if its source IP is in this range. (Otherwise it is not used.) This parameter is ignored if a config file is specified by --config.</p></td> </tr>
<tr> <td colspan="2">--config string</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>The path to the configuration file.</p></td> </tr>
<tr> <td colspan="2">--config-sync-period duration Default: 15m0s</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>How often configuration from the apiserver is refreshed. Must be greater than 0.</p></td> </tr>
<tr> <td colspan="2">--conntrack-max-per-core int32 Default: 32768</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Maximum number of NAT connections to track per CPU core (0 to leave the limit as-is and ignore conntrack-min).</p></td> </tr>
<tr> <td colspan="2">--conntrack-min int32 Default: 131072</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Minimum number of conntrack entries to allocate, regardless of conntrack-max-per-core (set conntrack-max-per-core=0 to leave the limit as-is).</p></td> </tr>
<tr> <td colspan="2">--conntrack-tcp-be-liberal</td> </tr> <tr> <td></td><td style="line-height: 130%; word-wrap: break-word;"><p>Enable liberal mode for tracking TCP packets by setting nf_conntrack …(trimmed)