Closed AkihiroSuda closed 3 weeks ago
Probably related to:
Confirm seeing this issue when using v0.25.2 on KIND cluster. Reverted to v0.25.1 for the time being.
I left this open. Changed how the parameter is passed it'll be fixed for the next release.
@rbrtbnfgl, @AkihiroSuda,
Can I ask the definition of "flannel.alpha.coreos.com/node-public-ip":
Thanks.
It could be the addressable IP but generally it should use in case of a node with multiple interface and helps to select Flannel the right one. This issue was introduced because it was using the public-ip
annotation and in case of public-ip-overwrite
it was changed with the addressable IP that could be not a specific IP of the node and that's why it was failing because there wasn't any interface with that IP. I moved the logic within a new annotation so the public-ip
is behaves as before and publuc-ip-overwrite
can work as expected. In case you don't have to define an interface that flannel should use with a node specific IP you can omit the new annotation and Flannel will choose the interface as before.
@rbrtbnfgl , thanks for the reply. In the case of KIND there's only one interface (eth0), but v0.25.2 has also failed with "No interface with given IP found after restarting a node" when the host restarted. Note this doesn't happen to v0.25.1. I suspect that could be something else because this shouldn't happen base on your replied,
This is how it should work with the fix. With the current release is not working as I explained. I think we'll release a new version with the right behavior.
Thanks, v0.25.3 works fine
Expected Behavior
flannel.alpha.coreos.com/public-ip-overwrite
should continue to work after restarting a nodeCurrent Behavior
Flannel v0.25.2 fails with
error looking up interface XXX.XXX.XXX.XXX: No interface with given IP found
after restarting a node, even whenflannel.alpha.coreos.com/public-ip-overwrite
is specified to allowXXX.XXX.XXX.XXX
.It was working in Flannel v0.25.1.
Possible Solution
Revert:
Steps to Reproduce (for bugs)
Checkout https://github.com/rootless-containers/usernetes/tree/gen2-v20240527.0
Apply the following update:
Initialize a node. This step should be executed with Rootless Docker, but Rootful Docker is fine too.
Restart the node, and see that the
kube-flannel
container fails:Context
Regression in v0.25.2
Your Environment