This message was deleted.
# k3s
a
This message was deleted.
b
There is no kubernetes API to do this. At your own risk, you could stop k3s service, modify the
node-ip
config and restart the k3s service. But there might be connectivity problems. This is a use case that is not tested
c
For a multi node cluster the best and I think correct thing is to remove a node and add it back in with the new ip. I have done with to reply all my controllers with new devices.
a
Thanks @bland-account-99790 I tried it after restart k3s service i got error
Failed to test data store connection: this server is a not a member of the etcd cluster.
looking for old IP Tried to remove
/var/lib/rancher/k3s/server/db/etcd/member/*
k3s start successfully but all resources have been removed. Thanks @cool-room-99795
613 Views