This message was deleted.

This IP swap behaviour only happens with

kubelet-arg: "node-ip=::"

- setting it to 0.0.0.0 instead causes ipv4 address at startup with no later change to ipv6

kubelet-arg: "node-ip=::"

tells the kubelet that you want to prefer ipv6 addresses. I’m not sure why it would start out as ipv4 and then change to ipv6, but this is all kubelet stuff - not k3s.

Thanks. I’ll try to repro using a more vanilla cilium or standard flannel to see if I can narrow it down and get to the bottom of it.