Skip to content

fix: Raise the IPAM quota defaults past what retention accrues - #131

Draft
scotwells wants to merge 1 commit into
mainfrom
chore/raise-ipam-default-quota
Draft

scotwells wants to merge 1 commit into
mainfrom
chore/raise-ipam-default-quota

Conversation

@scotwells

Copy link
Copy Markdown
Contributor

Summary

A network's fabric identity is claimed once and kept forever, so the platform project holding the tenant address pools accrues a claim for every network in the environment and never releases one.

The default of 100 was sized for a project's own claims, production reached 65 of it in seven days, and hitting 100 refuses every address allocation for every tenant.

This raises the claim default to 10000 and the pool default to 2500, and lifts both ceilings so an operator can still grant above the default.

Important

Production runs on a hand-raised grant of 500 today, which should come out once this default reaches it.

Test plan

  • A new project starts with the raised claim and pool limits
  • A project already granted above the default keeps its granted limit
  • Creating a network in production allocates an address rather than being refused
  • Operators can still grant above the default up to the new ceiling

A fabric identity is claimed once per network and retained forever, because
reissuing one would merge a new network into a dead one's routes. A project's
claim count therefore only rises, and the platform project holding the tenant
address pools carries a claim for every network in the environment rather than
its own.

The old default of 100 was sized for a project's own claims. Production reached
65 of it in seven days at a trailing rate of 21 a day, and reaching 100 fails
every address allocation for every tenant, not just the project that crossed
the line.

Key changes:
- Raise the IPClaim default to 10000 and the IPPool default to 2500
- Raise both ceilings so an operator can still grant above the default
- Record why the count only rises, so the next person sizing this knows
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant