In the previous journals (20251008, 20251009), I provided 2 issues why worker nodes are not ready. In this journal, if you see something like the journalctl logs below, the port that you’ve set in your configuration may be incorrect. If you’re using default ports, the controlplane is accessible via port 6443, not 6553 like below.
Oct 09 12:40:01 node01 kubelet[19656]: I1009 12:40:01.913322 19656 kubelet_node_status.go:75] "Attempting to register node" node="node01"
Oct 09 12:40:01 node01 kubelet[19656]: E1009 12:40:01.915028 19656 kubelet_node_status.go:107] "Unable to register node with API server" err="Post \"https://controlplane:6553/api/v1/nodes\": dial tcp 192.168.142.232:6553: connect: connection refused" node="node01"
Oct 09 12:40:05 node01 kubelet[19656]: E1009 12:40:05.210534 19656 eviction_manager.go:292] "Eviction manager: failed to get summary stats" err="failed to get node info: node \"node01\" not found"
Oct 09 12:40:08 node01 kubelet[19656]: E1009 12:40:08.696190 19656 controller.go:145] "Failed to ensure lease exists, will retry" err="Get \"https://controlplane:6553/apis/coordination.k8s.io/v1/namespaces/kube-node-lease/leases/node01?timeout=10s\": dial tcp 192.168.142.232:6553: connect: connection refused" interval="7s"
Oct 09 12:40:08 node01 kubelet[19656]: I1009 12:40:08.916706 19656 kubelet_node_status.go:75] "Attempting to register node" node="node01"
Oct 09 12:40:08 node01 kubelet[19656]: E1009 12:40:08.918669 19656 kubelet_node_status.go:107] "Unable to register node with API server" err="Post \"https://controlplane:6553/api/v1/nodes\": dial tcp 192.168.142.232:6553: connect: connection refused" node="node01"
Oct 09 12:40:09 node01 kubelet[19656]: E1009 12:40:09.026959 19656 event.go:368] "Unable to write event (may retry after sleeping)" err="Post \"https://controlplane:6553/api/v1/namespaces/default/events\": dial tcp 192.168.142.232:6553: connect: connection refused"To fix this, modify /etc/kubernetes/kubelet.conf.