This message was deleted.

Rancher is not required to run your workloads in downstream clusters. So, you are safe to take Rancher down and move it to a new server without affecting your production workloads. When I did the same as you ar trying to do, I also kept the same IP address of the Rancher server: 1. Stop Rancher container 2. Copy Docker volume data to new server 3. Shut down original Rancher server 4. Configure your DHCP server to assign original server's IP to the new one 5. Start the server and start Rancher - the same version you had on the original server (

docker run -d --restart=unless-stopped -p 80:80 -p 443:443 --privileged rancher/rancher:RANCHER_VERSION_TAG_GOES_HERE

) If you run production on your downstream clusters, consider moving Rancher management to it's own Kubernetes cluster for high availability: https://www.suse.com/c/rancher_blog/migrating-rancher-2-5-0-single-node-docker-install-to-a-ha-kubernetes-k3s-cluster/

@mysterious-airline-88624 Wow! I really appreciate your help! I was not sure about how the rancher really works, how it is different from the kubeadm, but now I understood. Thank you for the best explanation!