This message was deleted.
# generala
adamant-kite-43734
05/11/2025, 11:31 PMThis message was deleted.
c
creamy-pencil-82913
05/12/2025, 1:40 AMDon't do this. You cannot use an external VIP as the registration address when provisioning via Rancher. Rancher manages this for you by ensuring that a valid node (known as the init node) is used as the endpoint when joining additional nodes. The registration address is only needed when joining the cluster, not when starting after having joined, so this does not affect HA.
creamy-pencil-82913
05/12/2025, 1:43 AMYou're working too hard to fix something that shouldn't be an issue. Don't try to mess around with the server address or advertised addresses or stick kube-vip in the middle where Rancher doesn't expect it to be
creamy-pencil-82913
05/12/2025, 1:45 AMIt's a fixed registration address. Registration The addresses of servers are cached once the node joins, so as long as at least one is up they will start up fine. After join it's just a fallback in case none of the servers it was previously aware of are reachable.
g
gentle-planet-29331
05/12/2025, 2:56 PMOkay thank you very much for that detailed answer. I´ll drop this thought then. 🙂 I had some cases in my lab when I was breaking my test cluster in creative ways where I had to manually change the server IP from master1 (down) to master2 on a worker node which showed down in kubernetes and restart rke2-agent did nothing, that was why I was under the impression that having the registration IP HA would improve this.
26 Views