16 Commits (cd4ddedbc9782cbe9b5dcc411df2addae7b2f3b4)

Author	SHA1	Message	Date
Manuel Buil	30449e0128	Add 2>dev/null when checking nm-cloud systemd unit ... Signed-off-by: Manuel Buil <mbuil@suse.com>	11 months ago
Manuel Buil	a629db023c	Fail to start k3s if nm-cloud-setup is enabled ... Signed-off-by: Manuel Buil <mbuil@suse.com>	3 years ago
Brad Davidson	c824c3bcc1	Add support for multiple env files for systemd unit ... Signed-off-by: Brad Davidson <brad.davidson@rancher.com>	4 years ago
Akihiro Suda	732228fd15	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>	4 years ago
Adam Farden	86d2e2a5f8	[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>	4 years ago
Adam Farden	b4335630b7	[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	5 years ago
cryptk	f9dd8dedc8	Add a little extra delay between restart attempts ... This extra delay prevents systemd from determining that the service is restarting "too quickly".	5 years ago
galal-hussein	8188bc62aa	Add Restart=always to systemd unit	6 years ago
galal-hussein	c30c809642	Change systemd unit file target to network-online.target	6 years ago
William Zhang	22bd3a3ce7	🔧 nf_conntrack module ... Signed-off-by: William Zhang <zhang.wanmin@zte.com.cn>	6 years ago
Erik Wilson	1bc7042bd5	Fix systemd TimeoutStartSec ... Set TimeoutStartSec to 0 instead of infinity for systemd versions older than 229.	6 years ago
Matt Keas	f7e0017fed	Extend systemd start timeout for slow systems ... Cert generation may cause slow startup times for some systems such as the Raspberry Pi, set the systemd service TimeoutStartSec to Infinity to avoid startup timeouts.	6 years ago
Darren Shepherd	0414f97c78	Revert "Enable systemd ready notification for k3s server" ... This reverts commit c73e9187bb.	6 years ago
Erik Wilson	c73e9187bb	Enable systemd ready notification for k3s server ... Disables k8s generic api server systemd ready notification and send our own ready notification after server available and kubeconfig available.	6 years ago
Darren Shepherd	3f2a951564	Ensure that br_netfilter module is loaded	6 years ago
Darren Shepherd	126247b8b6	Add k3s.service unit file	6 years ago