This message was deleted.

Updating ips overall is a pain... even with RKE managed by a distant rancher, you can't change a node internal IP.

Well it is not updating a node ip it is about the configuration about the external datastore for k3s / rancher

Yeah i get it, however since you can't even update a node IP, updating the datastore IP to a whole cluster seems pretty hard to me

Full disclosure - I never tried k3s with external DB so I have no clue if this will work... try in non-prod first... For installation - per this doc: https://docs.k3s.io/datastore/ha#1-create-an-external-datastore I see this:

--datastore-endpoint="<mysql://username:password@tcp>(hostname:3306)/database-name"

For upgrades: https://docs.k3s.io/upgrades/manual#upgrade-k3s-using-the-installation-script So perhaps, during one of the upgrade method specify the

--datastore-endpoint

option Again - I have never done this so try in sandbox env and see what happens

It is easier than expected, tested & verified

sudo service k3s stop

edit:

/etc/systemd/system/k3s.service

sudo service k3s start

Thanks for your hints.