How is apiEndpoint field managed for each cluster?

Rancher 2.x
1

Despite have multiple kube-apiserver nodes, Rancher seems to pick a single “leader” node and reference it as apiEndpoint. Initially, I thought this was related to the cattle-system/cattle-cluster-agent pod phoning home, however, even after that pod was rescheduled to another host during failure, the apiEndpoint remained at the old value.

Are there any docs on what all this apiEndpoint is actually used for?

Any insight on how this is managed or how it can be changed to a different kube-apiserver K8s node?

Is there any reason this value isn’t a list of all kube-apiserver nodes in the cluster, rather than a single node? This seems like a single point of failure with a different cardinality than master nodes.

2

I’m not near my cluster to check, but if I recall correctly the apiEndpoint was the cluster internal IP for the kubernetes service in the default namespace. Check if kubectl get services -n default -o wide shows the apiEndpoint IP for a service named kubernetes. If so, then I think that Kubernetes load balances services IPs for all available pods, so it should be fine in that sense. Not sure I can tell you what Rancher uses that for, though.