github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/contrib/init/systemd/kubelet.service

24 lines
571 B
INI
Raw Normal View History

systemd example unit and environment files
2014-10-15 15:55:20 +00:00
[Unit]
Description=Kubernetes Kubelet Server
Documentation=https://github.com/GoogleCloudPlatform/kubernetes
Use docker.service not docker.socket in unit files Some distros, include RHEL and Fedora, are doing away with the docker socket by default in systemd units, for security reasons. Instead rely on the docker.service being started instead of socket activation.
2015-01-22 16:36:21 +00:00
After=docker.service cadvisor.service
Requires=docker.service
systemd example unit and environment files
2014-10-15 15:55:20 +00:00
[Service]
Change kubelet working dir to /var/lib/kubelet Some image based OS do not allow writing to /. Since the kubelet looks for .dockercfg files in the working dir and uses / as the working dir, this means one can never set a .dockercfg on those distros. This moves the kubelet working dir to /var/lib/kubelet, where the kubelet naturally does its work.
2015-01-27 16:34:45 +00:00
WorkingDirectory=/var/lib/kubelet
systemd example unit and environment files
2014-10-15 15:55:20 +00:00
EnvironmentFile=-/etc/kubernetes/config
EnvironmentFile=-/etc/kubernetes/kubelet
ExecStart=/usr/bin/kubelet \
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 \
Fix for default systemd startup of the kublet, also forcing the hard requirement for the parameter. Sans parameter the kubelet will fail silently trying to obtain service setting that are placed into the ENV of the PODS.
2015-02-20 02:10:24 +00:00
$KUBELET_API_SERVER \
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
$KUBELET_ADDRESS \
$KUBELET_PORT \
$KUBELET_HOSTNAME \
$KUBE_ALLOW_PRIV \
$KUBELET_ARGS
systemd example unit and environment files
2014-10-15 15:55:20 +00:00
Restart=on-failure
[Install]
WantedBy=multi-user.target