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 stream forwarding or round robin TCP,UDP 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.
The IP address for the proxy server to serve on (set to 0.0.0.0 for all interfaces)
If true cleanup iptables rules and exit.
The CIDR range of pods in the cluster. It is used to bridge traffic coming from outside of the cluster. If not provided, no off-cluster bridging will be performed.
How often configuration from the apiserver is refreshed. Must be greater than 0.
Maximum number of NAT connections to track (0 to leave as-is)
Idle timeout for established TCP connections (0 to leave as-is)
The Google Cloud Platform Service Account JSON Key to use for authentication.
The IP address for the health check server to serve on, defaulting to 127.0.0.1 (set to 0.0.0.0 for all interfaces)
The port to bind the health check server. Use 0 to disable.
If non-empty, will use this string as identification instead of the actual hostname.
If using the pure iptables proxy, the bit of the fwmark space to mark packets requiring SNAT with. Must be within the range [0, 31].
How often iptables rules are refreshed (e.g. '5s', '1m', '2h22m'). Must be greater than 0.
Burst to use while talking with kubernetes apiserver
QPS to use while talking with kubernetes apiserver
Path to kubeconfig file with authorization information (the master location is set by the master flag).
Maximum number of seconds between log flushes
If using the pure iptables proxy, SNAT everything
The address of the Kubernetes API server (overrides any value in kubeconfig)
The oom-score-adj value for kube-proxy process. Values must be within the range [-1000, 1000]
Which proxy mode to use: 'userspace' (older) or 'iptables' (faster). If blank, look at the Node object on the Kubernetes API and respect the 'net.experimental.kubernetes.io/proxy-mode' annotation if provided. Otherwise use the best-available proxy (currently iptables). If the iptables proxy is selected, regardless of how, but the system's kernel or iptables versions are insufficient, this always falls back to the userspace proxy.
Range of host ports (beginPort-endPort, inclusive) that may be consumed in order to proxy service traffic. If unspecified (0-0) then ports will be randomly chosen.
How long an idle UDP connection will be kept open (e.g. '250ms', '2s'). Must be greater than 0. Only applicable for proxy-mode=userspace