Skip to content

design-proposal(ip-address-claims): a platform that bills addresses bills claims #126

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Timofei Larkin (lllamnyp) merged 1 commit into from
Nov 11, 2026
Merged

design-proposal(ip-address-claims): a platform that bills addresses bills claims #126

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions design-proposals/ip-address-claims/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -629,9 +629,10 @@ double-assign a reserved EIP. The provider enforces the separation, which is why
tenant chart does not yet.
- **Metering follows the claim.** A held address is held whether or not a Service wears
it, and a placeholder in the driver's namespace belongs to no tenant workload. A platform
that meters LoadBalancer Services meters the wrong object once addresses are claims. The
`IPAddress` ledger is the unit of accounting: `claimRef` says whose, the conditions say
since when.
that meters LoadBalancer Services meters the wrong object once addresses are claims. A
platform that bills addresses bills claims, as storage bills `PersistentVolumeClaim`s.
The `IPAddress` ledger is the record behind the bill: `claimRef` says whose, the
conditions say since when.

## Upgrade and rollback compatibility

Expand Down