This message was deleted.
# rke2a
adamant-kite-43734
12/23/2025, 4:16 PMThis message was deleted.
n
numerous-country-20400
12/23/2025, 10:28 PM@creamy-pencil-82913 this was my initial issue and it turned out that i missunderstood the "node-external-ip" setting on the new server node. I thought, i use node-ip for the internal interface (cluster network) and node-external-ip for the ip i route to the server, public ip. But this was not the case as i found in the docs. If i set the node-external-ip to my public ip, the agents and other services will randomly use this ip to communicate to the servers kubeapi and other things - and this is what broke the cluster since i firewall the public api to not access any k8s ports (except 80/443)
numerous-country-20400
12/23/2025, 10:28 PMi'am yet not entirely sure this was all the cause yet.
numerous-country-20400
12/23/2025, 10:29 PMWhat do you expect when restoring a snapshot of a single-server cluster rke2-server on a different host (shutting down the old) with a new IP. i followed the guide in the docs https://docs.rke2.io/datastore/backup_restore#restoring-to-new-hosts and then i stopped rke2-agent on all agents, removed them from the cluster, added the new
server:rke2-agentnumerous-country-20400
12/23/2025, 10:30 PMIs this the expected way of "migrating a single server" setup to a new host?
11 Views