Asking what I am sure is a stupid question, but I want to update a cluster, changing some arguments to kubelet, and assumed i would try updating the config.yaml and restart the control plane nodes... however using systemctl to stop the rke2-server service seems to have stopped kubelet, but not the other k8s related processes. Is this expected behaviour? Is the "correct" way to perform this restart to use the bundled

rke2-killall.sh

or something else?

Just change the args and restart. All of the components except for kubelet and containerd are managed as static pods, and pods (or any other container started by containerd) don't get killed when containerd exits. If they need to be restarted in order to effect your configuration change, they will be when rke2 starts.

Thanks, I tried both ways, was unsure of what was "correct".