Hi everyone! Quick question, I accidentally started

rke2-server

service on an

rke2-agent

service node. It converted the node in the cluster to a control-plane node, which it shouldn't be. I removed the node (

kubectl delete node

), rebooted it and started rke2-agent again, which added it. As good as everything is fine now, but control-plane pods are still started on the node... I tried deleting the pods , but they always come back:

cloud-controller-manager-agent-001        0/1     Error       2              9m17s
etcd-agent-001                            0/1     Completed   14             5m10s
kube-apiserver-agent-001                  0/1     Error       19             5m10s
kube-controller-manager-agent-001         1/1     Running     2 (34m ago)    3m7s
kube-scheduler-agent-001                  1/1     Running     2 (34m ago)    3m6s

I thought etcd might be the problem, so I tried to annotate

kubectl annotate node agent-001 <http://etcd.k3s.cattle.io/remove=true|etcd.k3s.cattle.io/remove=true>

, but this did not work. How do I proceed?

$ sudo /usr/local/bin/rke2-uninstall.sh $ kubectl delete node <node> run the install again as agent

Hi @sparse-fireman-14239, thank you for this! I was hoping there was a way without the uninstall.sh 😅 as this is an active workload agent

There might be other methods, dunno.

I'm just wondering what keeps scheduling the pods again after I delete them

have you tried to run rke2-killall.sh and then to start rke2-agent (systemctl start rke2-agent)?

No I haven't, but I did reboot. Let me try.

I have been in the same boat due to terraform typo's. You will need to uninstall, then re-install for the node to come back into the cluster as a worker. Doesn't take long.

delete the control-plane component manifests from /var/lib/rancher/rke2/agent/pod-manifests

Thanks Brandon, should this happen again I'll try this approach!