Automated cherry pick of #7511: Clean up stale secondary IPs in IPPool when Node restarts #7538: Improve stale IP recycling in AntreaIPAM controller (#7538) #7571: Recycle IPs in IPPools for terminated Pods (#7571) #7584
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…7511) When a Kubernetes Node reboots and the OVSDB file is not properly restored, the primary and secondary OVS ports are lost. Pods may temporarily appear as "unknown" and later get recreated with new container IDs. The cleanup of secondary interfaces during agent restart relies on the InterfaceStores being initialized with existing OVS ports. If the OVSDB file is missing, the primary InterfaceStore is empty, which prevents the secondary InterfaceStore from initializing correctly. Consequently, secondary IPs assigned to old Pods (with previous container IDs) are not deleted, leaving stale entries in the IPPool. This change adds logic to periodically verify all IPPool allocations and release any secondary IPs associated with non-existing container IDs. This also covers the case where a Pod is recreated with the same name on another Node and has any secondary IPs. Signed-off-by: Lan Luo <[email protected]>
When a Node is deleted, the CNI DEL command may not be invoked for Pods running on that Node. As a result, antrea-agent cannot release their IPs, leaving stale entries in the IPPool. To mitigate this, increase the IP recycle interval from 10 minutes to 1 minute. Additionally, add a benchmark test for the IP recycle function and refine its implementation based on benchmark results to reduce memory allocations and improve cleanup performance. Signed-off-by: Lan Luo <[email protected]>
* Recycle IPs in IPPools for terminated Pods * Improves the logging behavior to avoid emitting repetitive messages every minute Signed-off-by: Lan Luo <[email protected]>
luolanzone
added
kind/cherry-pick
Contributor
Author
|
/test-all |
antoninbas
approved these changes
Nov 24, 2025
luolanzone
deleted the
automated-cherry-pick-of-#7511-#7538-#7571-upstream-release-2.4
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry pick of #7511 #7538 #7571 on release-2.4.
#7511: Clean up stale secondary IPs in IPPool when Node restarts
#7538: Improve stale IP recycling in AntreaIPAM controller (#7538)
#7571: Recycle IPs in IPPools for terminated Pods (#7571)
For details on the cherry pick process, see the cherry pick requests page.