Skip to content

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

@mcbenjemaa

Description

@mcbenjemaa

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions