Skip to content

Setting a /32 or /128 IP blockSize on a pool not possible #28637

@CallMeFoxie

Description

@CallMeFoxie

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/agentCilium agent related.area/multipoolAffects Multi-Pool IPAMkind/bugThis is a bug in the Cilium logic.kind/community-reportThis was reported by a user in the Cilium community, eg via Slack.pinnedThese issues are not marked stale by our issue bot.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions