Conversation
Consumers currently claim IP space by naming a pool or matching pools by label, which forces them to understand the platform's pool topology and makes claim manifests non-portable across environments. This enhancement proposes IPClass: a platform-owned policy object (analogous to a Kubernetes StorageClass) that names a kind of address space and the rules for handing it out. Consumers claim by class name; the platform decides which pools back a class and how blocks are placed. The proposal separates intent (the claim), policy (the class), and topology (the pool); makes cross-project sharing transparent; establishes a clean platform/consumer ownership boundary; gives quota and utilization a natural unit; and reserves a provisioner seam for future external and cloud address sources. It is fully backward compatible.
scotwells
force-pushed
the
feat/ip-class-enhancement
branch
from
July 2, 2026 13:22
13e18f2 to
c177883
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What this proposes
Today a consumer who wants IP space has to know how the platform carved it — an
IPClaimeither names a specificIPPoolor matches pools by label. That forces the person asking for an address to understand pool names, label conventions, and which project owns which range, and it bakes environment-specific topology into every claim, so a claim that works in staging fails in production.IPClassadds the missing layer of indirection: a platform-owned policy object, the direct analog of a KubernetesStorageClass. It names a kind of address space and the rules for handing it out — which pools back it, how blocks are placed, allowed prefix sizes, what happens on release. Consumers stop saying "give me a /24 fromprod-backbone-us-east" and say "give me a /24 of classpublic-egress."Why it's a better shape
provisionerfield reserves a seam for future BYOIP, cloud, and external address sources without changing the claim experience.Scope
Fully backward compatible and additive. Claiming by class name becomes the standard path; label selection on the claim is deprecated in favor of the class; naming a pool directly remains as an advanced escape hatch.
Contents
This PR is the proposal only —
docs/enhancements/ip-class.md(summary, motivation, the CLI experience, design details, migration, drawbacks, alternatives). The implementation lands separately in #72. A follow-up for catalog-driven per-project class distribution is drafted separately.Status
Draft for review.