steep-manchester-31195
12/22/2022, 9:59 AMrke2-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?sparse-fireman-14239
12/22/2022, 2:30 PMsteep-manchester-31195
12/22/2022, 2:31 PMsparse-fireman-14239
12/22/2022, 2:31 PMsteep-manchester-31195
12/22/2022, 2:32 PM<http://rke2.io/node-config-hash|rke2.io/node-config-hash>: redacted====
cold-egg-49710
12/22/2022, 2:46 PMsteep-manchester-31195
12/22/2022, 2:46 PMhallowed-breakfast-56871
12/22/2022, 6:49 PMcreamy-pencil-82913
12/22/2022, 7:30 PMsteep-manchester-31195
01/24/2023, 3:20 PM