k3os and systemd: What is the impact of kubelet's stop timeout on pod termination?
k3os ↔ systemd: graceful kubelet shutdown The goal is to understand how the stop timeout configured in the kubelet.service unit influences the termination of running pods when a k3os node is powered down or reset. In k3os the kubelet is launched as a systemd service with TimeoutStopSec=0 by default, meaning that a SIGTERM is followed immediately by a SIGKILL