From cfe8949c3c123b00830c3bd1e9837c1a77a7a791 Mon Sep 17 00:00:00 2001 From: Timofei Larkin Date: Tue, 10 Nov 2026 18:41:58 +0300 Subject: [PATCH] design-proposal(ip-address-claims): a platform that bills addresses bills claims The prose rewrite in 82cd418 dropped this clause from "Metering follows the claim", which left the ledger sentence reading as if IPAddress objects were the billable unit. The clause is restored, and the ledger is described as the record behind the bill. Assisted-by: LLM Signed-off-by: Timofei Larkin --- design-proposals/ip-address-claims/README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/design-proposals/ip-address-claims/README.md b/design-proposals/ip-address-claims/README.md index de5922e..ee9c179 100644 --- a/design-proposals/ip-address-claims/README.md +++ b/design-proposals/ip-address-claims/README.md @@ -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