This message was deleted.
# k3s
a
This message was deleted.
q
I can't really think of any case where any of my k3s clusters have died because of a IP address change ... what kind of problems are you experiencing?
I would have thought the only thing needed was to change the IP in your kubeconfig to point to the new IP ... 🤔
a
The device changed IP (DHCP) and k3s server stopped working. v1.26.11+k3s2 Rancher-launched
Changing the IP in the KUBECONFIG does not help as k3s server is broken.
q
Weird. Never experienced it, so don't have any more tips for you I'm afraid.
f
@aloof-country-66308 Can you reassign the same IP back to the server perhaps? Shouldn't be down due to an IP change
Also DHCP is not good if you're using that
a
I have reset the device and will reproduce the IP change to see in detail what happens. I expected it to be plug-and-play so it can be pre-configured and shipped to a remote location...