This message was deleted.
# k3s
a
This message was deleted.
c
you already started the cluster with the default cidrs; if you want to change it you need to uninstall or at least wipe the datastore.
you can’t change the cidrs after the cluster has been started, its already assigned IPs from the initial ones to various nodes and pods and services.
a
when I start the cluster with these values, k3s binary fails and the error that I see is
flannel exited: failed to acquire lease
I'm creating an entirely new cluster. I don't want t o change an existing one
c
You’re not creating a new one, if you were creating a new one it wouldn’t tell you that the node already had a PodCIDR assigned from the default cidr block.
Are you perhaps pointing it at an external datastore that you forgot to wipe?
a
I really am. I rant the k3s-uninstall script, rebooted and started again
c
if not then you have data left on disk from a previous install.
make sure /var/lib/rancher/k3s/server/db is empty
a
OK
c
or I guess /foo/server/db in your case
thats’ probably part of your problem, the uninstall script doesn’t know about your custom data-dir so it won’t wipe things out of it. It only wipes things from the default paths
a
That was it, thanks again, @creamy-pencil-82913.