k3s/k3s.service

[Unit]
Description=Lightweight Kubernetes
Documentation=https://k3s.io
After=network-online.target
Wants=network-online.target

[Service]
Type=notify
EnvironmentFile=-/etc/systemd/system/k3s.service.env
ExecStart=/usr/local/bin/k3s server
KillMode=process
Delegate=yes
# Having non-zero Limit*s causes performance problems due to accounting overhead
# in the kernel. We recommend using cgroups to do container-local accounting.
LimitNOFILE=1048576
LimitNPROC=infinity
LimitCORE=infinity
TasksMax=infinity
TimeoutStartSec=0
Restart=always
RestartSec=5s

[Install]
WantedBy=multi-user.target
Add k3s.service unit file 2019-01-24 18:30:38 +00:00			`[Unit]`
			`Description=Lightweight Kubernetes`
			`Documentation=https://k3s.io`
Change systemd unit file target to network-online.target 2019-04-29 23:28:58 +00:00			`After=network-online.target`
[systemd] really wait for network to come online (#1665) Wants= is required to actually set the dependency on network-online.service After= is required or k3s.service will be started at the same time as network-online.service In network environments with slow DHCP, both are required to ensure valid network configuration for k3s Signed-off-by: Adam Farden <adam@farden.cz> 2020-09-26 08:44:06 +00:00			`Wants=network-online.target`
Add k3s.service unit file 2019-01-24 18:30:38 +00:00
			`[Service]`
🔧 nf_conntrack module Signed-off-by: William Zhang <zhang.wanmin@zte.com.cn> 2019-04-18 01:27:20 +00:00			`Type=notify`
systemd unit: make EnvironmentFile optional Previously, k3s.service was failing when the EnvironmentFile does not exist: ``` Feb 02 17:17:30 suda-ws01 systemd[1]: k3s.service: Failed to load environment files: No such file or directory Feb 02 17:17:30 suda-ws01 systemd[1]: k3s.service: Failed to run 'start' task: No such file or directory Feb 02 17:17:30 suda-ws01 systemd[1]: k3s.service: Failed with result 'resources'. Feb 02 17:17:30 suda-ws01 systemd[1]: Failed to start Lightweight Kubernetes. ``` ref: https://unix.stackexchange.com/questions/404199/documentation-of-equals-minus-in-systemd-unit-files Signed-off-by: Akihiro Suda <akihiro.suda.cz@hco.ntt.co.jp> 2021-02-02 08:18:38 +00:00			`EnvironmentFile=-/etc/systemd/system/k3s.service.env`
Add k3s.service unit file 2019-01-24 18:30:38 +00:00			`ExecStart=/usr/local/bin/k3s server`
			`KillMode=process`
			`Delegate=yes`
[systemd] Add value to LimitNOFILE due to performance problems When k3s is installed on an OS with default high ulimits, performance issues can be observed. This was discovered on CoreOS where the default value is 1073741816. Symptoms include very slow file operations such as installing a Rook/Ceph cluster will take ~6 hours instead of ~10 minutes. A google search for 'container LimitNOFILE' will show that most major projects set this already, including the (unused) containerd systemd unit found in this repository at /vendor/github.com/containerd/containerd/containerd.service k3OS is not affected becuasse the default there is already 1048576. See description in coreos/fedora-coreos-tracker#329 2020-05-03 07:27:54 +00:00			`# Having non-zero Limit*s causes performance problems due to accounting overhead`
			`# in the kernel. We recommend using cgroups to do container-local accounting.`
			`LimitNOFILE=1048576`
Add k3s.service unit file 2019-01-24 18:30:38 +00:00			`LimitNPROC=infinity`
			`LimitCORE=infinity`
			`TasksMax=infinity`
Fix systemd TimeoutStartSec Set TimeoutStartSec to 0 instead of infinity for systemd versions older than 229. 2019-04-17 18:27:03 +00:00			`TimeoutStartSec=0`
Add Restart=always to systemd unit 2019-05-08 00:54:40 +00:00			`Restart=always`
Add a little extra delay between restart attempts This extra delay prevents systemd from determining that the service is restarting "too quickly". 2019-07-22 22:03:36 +00:00			`RestartSec=5s`
Add k3s.service unit file 2019-01-24 18:30:38 +00:00
			`[Install]`
			`WantedBy=multi-user.target`