Flight Log / Azure/azure-container-networking #3697
Fix CNS IP demand overcounting by filtering terminal Pods in IPAMv2 — a GitHub Copilot (GitHub) bot flight
The GitHub Copilot bot (GitHub) opened this pull request in Azure/azure-container-networking on Jun 4, 2025; merged after rework in 4.9 d: +252 −133, 6 files, 10 reviews.
Flown by
- Lines
- +252 −133
- Files
- 6
- Commits
- 6
- Reviews
- 10 (3 ✕)
- To merge
- 4.9 d
- Task
- fix
Line and file counts are summed per commit from the AIDev dataset; GitHub's net diff can be smaller.
GitHub Copilot fixed a bug in Azure Container Networking where CNS, under IPAMv2, overcounted IP demand by including Pods in Succeeded or Failed states. The change filters those Pods out across six files. It received ten reviews and three change requests, including a lint failure on adapter.go. It merged after rework at 118.22 hours.
“Linting is failing on the changed files and needs to be fixed: ``` cns/ipampool/v2/adapter.go:45: File is not `gci`-ed with --skip-generated -s standard -s default (gci)”
— from the review (source)
From the pull request description
When configured for IPAMv2, CNS watches Pods to calculate IP demand for dynamic Podsubnet scenarios. However, CNS was overcounting the IP demand by including Pods in terminal states (Succeeded/Failed), even though these Pods no longer have network sandboxes and their IPs have been released. ## Prob…
Excerpt (first 300 characters) — the full description is on GitHub.
View the pull request on GitHub →
This is your flight? Claim it — sign in with GitHub. Ownership is proven by the sign-in: the account that opened the PR is the only one that can claim it.
Flight timeline
Read next
Cite this flight: AgentRiders Flight Log, Azure/azure-container-networking#3697, record updated Nov 3, 2026, https://agentriders.com/logs/Azure/azure-container-networking/3697/
Data from public GitHub activity; this page is not affiliated with GitHub or the repository.