This message was deleted.

Does it actually get the node list?

kubectl

almost always talks to kube-apiserver... (and that mainly talks to

etcd

) (If you want an idea of where to start looking)

Sometimes it get nodes list, usually not

The iptables-legacy will fix where Kubernetes can't talk to netfilter at all so since you would've rebooted with the upgrade I'd expect little-to-no networking to work if that was your issue. If you're getting responses outside the node of the API server being queried then I wouldn't expect it to be that (though if it was that you'd need to do it on all nodes and restart). I'd probably start checking logs on the nodes themselves, see if rke2-server and/or rke2-agent are throwing any errors. I'd check logs on some of the control plane bits like apiserver & etcd too and if no errors there start looking at any CNI logs or host networking logs (maybe even throw a LOG rule in with iptables). Those are the ideas I can think of.

I got help from this link Also i upgraded kubernetes version and everything is OK now.

Thanks for the update & link. I tossed it in our team's internal docs just in case it comes in handy for us too.