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

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

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

[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`

			`[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 \`
			`$KUBE_ETCD_SERVERS \`
			`$KUBE_PROXY_ARGS`
systemd example unit and environment files 2014-10-15 15:55:20 +00:00			`Restart=on-failure`

			`[Install]`
			`WantedBy=multi-user.target`