Access the Rancher Agent/Node: ◦ If Rancher agent/node is running as a Docker container, you can access it using the following command: ▪︎ In bash “docker exec -it <agent_container_id_or_name> sh” Update the Rancher Agent/Node Configuration: • The configuration file for the Rancher agent/node is typically located in the /etc/rancher/ directory. The exact location might vary based on your installation method. • Look for a configuration file, often named config.json or similar. Edit the Configuration File: • Use a text editor to open the configuration file. For example: ◦ In bash “vi /etc/rancher/config.json” ▪︎ Update the URL field in the configuration file with the new Rancher server URL. Restart the Rancher Agent/Node: • After updating the configuration, restart the Rancher agent/node to apply the changes. ◦ In bash “docker restart <agent_container_id_or_name>” ▪︎ Replace <agent_container_id_or_name> with the actual ID or name of your Rancher agent/node container. Verify the Connection: • Check the logs of the Rancher agent/node to ensure that it is connecting to the new Rancher server without errors. ◦ In bash “docker logs <agent_container_id_or_name>” ▪︎ Look for log entries indicating a successful connection to the Rancher server.

So the problem I'm running into is that the changes I make to the config.json are being discarded as soon as the container is started up, so it must be pulling the running config from somewhere else

oh wait, you're not using elemental

k3s node?

You poke around

/var/lib/rancher/rke/

?

I found some

kube_config_cluster.yml

files but they all point to the server address on port 6443 so I'm not sure what those are for

Is there any way to change a node's server address from the UI before changing the server address itself?