This message was deleted.

Agents run a client load-balancer that can connect them to any of the servers. The registration endpoint (--server flag/config value) is only used for the initial connection to the cluster. Once it’s joined it monitors the apiserver endpoint list and maintains connections to all of the servers. You can see this occurring in the agent logs.

What about loadbalancing external access to the kube-apiserver, say from a non-rancher gitops mgmt server like argocd or fluxcd running in a separate mgmt cluster?

the same thing would work fine with a round-robin DNS record pointing at the control plane. The load-balancer provides very little value.

the only thing is that with DNS you cannot know if one of the masters is down. But yeah now i understand more, thank you very much! Do you know where I can find more info on how the rke2-agent keeps track of the master nodes, I suppose if one master is not available the rke2-agent will also notice it right? Is the registration endpoint then after the node is added into the cluster not used anymore then? or it is also used to keep track of the masters?