Pensionsmyndigheten customer suggested an update in our documentation to prevent race conditions in HA setups when using F5 load balancer. "They encounter random join failures for additional rke2 master nodes, as he described as follows: The problem is that rke2 immediately starts to listen to port 9345 when the rke2-server service is started (even though it has not completed (or even started) the installation process to be a functioning member of the cluster. This fools the load balancer into thinking that the new node is ready for requests on port 9345 while only the first node can actually respond to requests for joining the cluster. We solved this by adding additional port monitoring on port 6443 to determine if the nodes are ready in the load balancer."
…ation Address"
Pensionsmyndigheten customer suggested an update in our documentation to prevent race conditions in HA setups when using F5 load balancer. "They encounter random join failures for additional rke2 master nodes, as he described as follows: The problem is that rke2 immediately starts to listen to port 9345 when the rke2-server service is started (even though it has not completed (or even started) the installation process to be a functioning member of the cluster. This fools the load balancer into thinking that the new node is ready for requests on port 9345 while only the first node can actually respond to requests for joining the cluster. We solved this by adding additional port monitoring on port 6443 to determine if the nodes are ready in the load balancer."