Have a k3s cluster that was created from Rancher UI several months ago. Recently one of the etcd / control plane node shows (in Cluster Management screen):

Configuring bootstrap node(s) custom-1ca8010bce3f: waiting for probes: kube-controller-manager, kube-scheduler

kubectl get nodes

shows everything is normal. K3s version: v1.23.17+k3s1 I need some help understanding where the issue is?

kube-controller-manager is what gets status and changes it so kubectl knows what's going on. If it's horked, you won't see updates. So you could scale deployments up & down and it'd all still show whatever it was to start with.

I’m guessing it’s related to this: https://github.com/rancher/rancher/issues/41125#issuecomment-1506620040

@gray-lawyer-73831 Thank you! that was it.