k3s/contrib/init/systemd/kube-proxy.service

[Unit]
Description=Kubernetes Kube-Proxy Server
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
After=network.target

[Service]
EnvironmentFile=-/etc/kubernetes/config
EnvironmentFile=-/etc/kubernetes/proxy
ExecStart=/usr/bin/kube-proxy \
	    $KUBE_LOGTOSTDERR \
	    $KUBE_LOG_LEVEL \
	    $KUBE_MASTER \
	    $KUBE_PROXY_ARGS
Restart=on-failure
LimitNOFILE=65536

[Install]
WantedBy=multi-user.target
systemd example unit and environment files 2014-10-15 15:55:20 +00:00			`[Unit]`
			`Description=Kubernetes Kube-Proxy Server`
			`Documentation=https://github.com/GoogleCloudPlatform/kubernetes`
Do no start kube-proxy until after network is started https://bugzilla.redhat.com/show_bug.cgi?id=1200919 The kube-proxy will die if it starts before the network. 2015-03-11 16:08:11 +00:00			`After=network.target`
systemd example unit and environment files 2014-10-15 15:55:20 +00:00
			`[Service]`
			`EnvironmentFile=-/etc/kubernetes/config`
			`EnvironmentFile=-/etc/kubernetes/proxy`
			`ExecStart=/usr/bin/kube-proxy \`
Do not use {} in systemd environment variables From the systemd man page: Use "${FOO}" as part of a word, or as a word of its own, on the command line, in which case it will be replaced by the value of the environment variable including all whitespace it contains, resulting in a single argument. Use "$FOO" as a separate word on the command line, in which case it will be replaced by the value of the environment variable split at whitespace, resulting in zero or more arguments. Since we want people to be able to use these for multiple arguments we need to make sure we don't use {} around the env vars... 2015-02-05 16:36:55 +00:00			`$KUBE_LOGTOSTDERR \`
			`$KUBE_LOG_LEVEL \`
update example systemd files to be more obvious only set the etcd servers in the apiserver config set the --master= in the global config still need --api_servers= different in kubelet because, ummmm, we do comment out the apiserver config in controller and scheduler, not needed point the proxy to api, not to etcd 2015-03-20 19:49:58 +00:00			`$KUBE_MASTER \`
Do not use {} in systemd environment variables From the systemd man page: Use "${FOO}" as part of a word, or as a word of its own, on the command line, in which case it will be replaced by the value of the environment variable including all whitespace it contains, resulting in a single argument. Use "$FOO" as a separate word on the command line, in which case it will be replaced by the value of the environment variable split at whitespace, resulting in zero or more arguments. Since we want people to be able to use these for multiple arguments we need to make sure we don't use {} around the env vars... 2015-02-05 16:36:55 +00:00			`$KUBE_PROXY_ARGS`
systemd example unit and environment files 2014-10-15 15:55:20 +00:00			`Restart=on-failure`
Fix to address issue #5461 kube-proxy too many files open https://github.com/GoogleCloudPlatform/kubernetes/issues/5461 2015-03-17 15:13:25 +00:00			`LimitNOFILE=65536`
systemd example unit and environment files 2014-10-15 15:55:20 +00:00
			`[Install]`
			`WantedBy=multi-user.target`