-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Open
Labels
area/agentCilium agent related.Cilium agent related.area/multipoolAffects Multi-Pool IPAMAffects Multi-Pool IPAMkind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.kind/community-reportThis was reported by a user in the Cilium community, eg via Slack.This was reported by a user in the Cilium community, eg via Slack.pinnedThese issues are not marked stale by our issue bot.These issues are not marked stale by our issue bot.
Description
Is there an existing issue for this?
- I have searched the existing issues
What happened?
Similar to #24351 but in multi-pool mode we sometimes use /32 (or /128 for that matter) single-IP pools for stuff like reserved IPs or IPs with special use. However cilium does not use the first and last IP of the pool, meaning the smallest is /30 and still wastes at least two IPs per block. We use eBGP so the "first and last IPs" are of no concern to us.
Since the patch for LB-IPAM is in the works to improve this, the code should be reusable for normal pod IPAM as well.
Cilium Version
1.15.0 branch
Kernel Version
5.15.0
Kubernetes Version
1.27.1
Sysdump
No response
Relevant log output
No response
Anything else?
No response
Code of Conduct
- I agree to follow this project's Code of Conduct
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/agentCilium agent related.Cilium agent related.area/multipoolAffects Multi-Pool IPAMAffects Multi-Pool IPAMkind/bugThis is a bug in the Cilium logic.This is a bug in the Cilium logic.kind/community-reportThis was reported by a user in the Cilium community, eg via Slack.This was reported by a user in the Cilium community, eg via Slack.pinnedThese issues are not marked stale by our issue bot.These issues are not marked stale by our issue bot.