4 ms·
k3s has no direct relationship to systemd, I'm not sure what things not working you are referring too. k3s has full flexibility to change any k8s option or com
by darren0 7y ago
k3s has no direct relationship to systemd, I'm not sure what things not working you are referring too.
k3s has full flexibility to change any k8s option or component, it merely defaults to settings to meet it's goals of being a simple, lightweight, and secure distro.
- moondev 7y ago> k3s has no direct relationship to systemd Exactly, this differs from every kubeadm bootstrapped cluster which uses systemd to run the kubelet, as well using common config locations and behavior. > k3s has full flexibility to change any k8s option or component Quick Example: How do you change the kubelet's cgroup-driver? This looks to be hard-coded into the k3s binaries. https://github.com/rancher/k3s/blob/c79743d4c3d9f2d21b352ed78a5d64e0a8e00263/pkg/daemons/agent/agent.go#L68 https://github.com/rancher/k3s/blob/c79743d4c3d9f2d21b352ed7...