test(quota): qualify three-application distributed quotas - #127
Draft
nerdalert wants to merge 1 commit into
Draft
Conversation
Exercise three Basic Auth subjects through one shared endpoint and verify independent subject-keyed quotas across two consumer gateways. Preserve the existing routing, concurrency, expiry, restart, outage, NetworkPolicy, evidence, and cleanup coverage while removing the temporary identity-gateway design. Signed-off-by: Brent Salisbury <bsalisbu@redhat.com>
nerdalert
force-pushed
the
fix/three-app-distributed-quota
branch
from
September 7, 2026 19:55
620ea90 to
a185c14
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
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.
Summary
Extends the distributed token-quota topology and first-class qualification to prove three independent application quotas through one shared consumer endpoint.
application-a,application-b, andapplication-cauthenticate with Basic Auth on the same listener. Praxis publishes the verified subject privately; Praxis AI uses that subject as the quota key; Grid routes admitted requests across the shared west, central, and east provider overlay.This keeps three responsibilities separate:
What the qualification proves
Topology changes
key: authenticated_subjectwith one common rule and Valkey namespace; the verified subject partitions the ledger securely.Quota contract
Admission is reservation-based because actual response usage is unknown before routing. The enforced invariant is:
Settlement records actual usage after the response. Actual settled usage may exceed the reservation estimate without indicating over-admission. Provider distribution is sampled independently from tight quota boundaries.
Cross-repository dependencies
This PR is the Grid qualification and reference topology for a contract implemented across repositories:
AuthenticatedIdentity.key: authenticated_subject, consumes that trusted identity, and hashes it into an opaque quota key.The identity type is authentication-method-neutral. Basic Auth enables this demo now, while JWT/OIDC/OAuth-backed authentication can publish the same identity for reuse by the AI quota filter.
Related to #101 and praxis-proxy/ai#121.
Depends on praxis-proxy/praxis#1108 and praxis-proxy/ai#980.
Validation
Two fresh Kind qualifications passed all 9 scenarios with automatic teardown. Static validation included xtask tests, workspace Clippy, formatting,
make test,make doc,make lint, Forge validation, andgit diff --check.Evidence and generated
.forge.resolved.*.yamlfiles are excluded from the commit.Landing order
Keep this PR open until Praxis #1108 is released and AI #980 consumes that release. Then rebuild the feature-enabled AI image from committed dependencies and rerun the qualification before merge.
Companion demo: praxis-proxy/demos#20.