This message was deleted.

In my experience, I've built external Nginx as proxy server to all of the cluster nodes, and make the SSL termination in the Nginx. I set the registration address to the vhost name of the nginx. So, full secure of the connection with domain name, no need to change the registration IP, just use the domain that handled by the reverse proxy. Even better, use redundant Nginx using corosync to build HACluster no single point of failure

Your are instaling RKE2 befor importing it to rancher manager? In this case i would to rke2 + kube-vip and use tke VIP address for the server join uri. But i am stuck with the registered RKE2.

In my conditions, just OS then using the registration link to add the cluster. Is the VIP changes? I think better use domain that point to the VIP, and it could use DNS record, also check the registration URL in the RAncher manager, is the same with VIP address or not