Hello, I try to setup a RKE2 Cluster (3M - 2W). But the Cluster starts only working after reboot after setup, and when I later reboot a node then this node is failing again. The RKE-Server Log shows me that line: Waiting to retrieve kube-proxy configuration; server is not ready: https://127.0.0.1:9345/v1-rke2/readyz: 500 Internal Server Error Node Configuration looks like this:

"advertise-address": "10.10.255.103"

"cni": "none"

"disable":

- "rke2-ingress-nginx"

"disable-cloud-controller": true

"disable-kube-proxy": false

"disable-network-policy": false

"flannel-iface": "eth1"

"kube-controller-manager-arg": "flex-volume-plugin-dir=/var/lib/kubelet/volumeplugins"

"kubelet-arg":

- "cloud-provider=external"

- "volume-plugin-dir=/var/lib/kubelet/volumeplugins"

"node-ip": "10.10.255.103"

"node-name": "k8s-test-control-plane-3"

"node-taint":

- "<http://node-role.kubernetes.io/control-plane:NoSchedule|node-role.kubernetes.io/control-plane:NoSchedule>"

"server": "<https://10.10.255.101:9345>"

"tls-san":

- "195.201.20.2"

"token": "xxxx"

"write-kubeconfig-mode": "0644"

Info: Currently no LB is between Nodes - Server is the first node and CNI: node is because I setup calico typha operator after cluster init (on setup time the first node has the default cni)

Just out of curiosity, does systemctl restart rke2-server help?

No it dosen't help - only a server restart...