Skip to content

Reusing IP addresses immediately after they've been released causes issues during rolling upgrades #332

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mcbenjemaa opened this issue Apr 9, 2025 · 0 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@mcbenjemaa
Copy link
Member

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

@mcbenjemaa mcbenjemaa added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 9, 2025
@schrej 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
@schrej schrej added kind/bug Categorizes issue or PR as related to a bug. and removed kind/feature Categorizes issue or PR as related to a new feature. labels Apr 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants