This message was deleted.
# rke2a
adamant-kite-43734
05/04/2022, 3:47 PMThis message was deleted.
c
creamy-pencil-82913
05/04/2022, 4:03 PMThe ingress needs 80 and 443 for anything you want to publish out of the cluster. The control-plane wants 9345 and 6443, but those are only used when bootstrapping new nodes into the cluster.
👍 1
r
rapid-helmet-86074
05/04/2022, 4:35 PMIf you've got control of your DNS I found it easier to just create a hostname with multiple A records for each control plane node and add them as they were ready and not messing with a load balancer.
c
creamy-pencil-82913
05/04/2022, 5:01 PMyeah, that is usually my recommendation as well
m
magnificent-caravan-81252
05/04/2022, 5:42 PMOh interesting - so just create DNS records pointing directly at the nodes in order of node priority or something? Or did you create a separate subdomain for each node?
magnificent-caravan-81252
05/04/2022, 5:43 PMAnd if I go that route, what would I put in the kubeconfig file for server?
r
rapid-helmet-86074
05/04/2022, 5:44 PMYou'd put the new DNS hostname in the kubeconfig file.
rapid-helmet-86074
05/04/2022, 5:44 PMYou can't do priority, it will round robin.
m
magnificent-caravan-81252
05/04/2022, 5:45 PMOkay, so just one hostname/subdomain. Thanks for your help!
w
wonderful-helicopter-16401
05/06/2022, 1:13 AMGreat tip! I don't know why I didn't think of that. So easy for my dev nodes.
b
bland-jackal-22983
05/07/2022, 9:39 AMit will round robin.i am curious how this works. if we point it to a specific node, then the traffic will all go to the api server on that node?
c
creamy-pencil-82913
05/07/2022, 6:07 PMThe control-plane load balancer is only used by agents when joining the cluster, after that they use an internal load-balancer to communicate with the servers.
creamy-pencil-82913
05/07/2022, 6:09 PMSo if you point it at one node, yes that one node would always need to be available for new nodes to join the cluster.
🙏 1
👍 1
5 Views