You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
On K8s upgrades, the new and old nodes are part of a cluster until the new nodes become ready.
There is a race condition where the IP is the same, which confuses the API server and prevents the old nodes from being cleaned up.
We are sure that this won't happen if we prevent the use of an already released IP immediately.
Using released IPs will be possible after some Delays like 5m
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
/kind feature
The text was updated successfully, but these errors were encountered:
schrej
changed the title
Released IP should be used again after some delay.
Reusing IP addresses immediately after they've been released causes issues during rolling upgrades
Apr 9, 2025
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
On K8s upgrades, the new and old nodes are part of a cluster until the new nodes become ready.
There is a race condition where the IP is the same, which confuses the API server and prevents the old nodes from being cleaned up.
We are sure that this won't happen if we prevent the use of an already released IP immediately.
Using released IPs will be possible after some Delays like 5m
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
/kind feature
The text was updated successfully, but these errors were encountered: