Quotas — Now Organized by Service #252
yahyafakhroji
started this conversation in
Changelog
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Quotas are now organized by the service that owns them — Networking, DNS, Platform Core, Organization & Projects, and more — with each group collapsible and labeled with human-readable names and descriptions, instead of a flat list of raw internal resource keys.
Key Improvements
1. Service-Grouped Layout
Quotas are now organized under their owning service, making it much easier to understand which limits belong to which part of the platform. Each group shows a resource count badge so you always know how many quotas are in scope at a glance.
2. Human-Readable Names & Descriptions
Gone are raw CRD keys like
networking.datumapis.com/httpproxies. Every quota now displays its display name and a plain-language description, so you know exactly what you're looking at without needing to cross-reference internal docs.3. At-Risk Warnings
Quotas approaching their limit are surfaced first within each group, with a near-limit badge on the group header and a "Request Limit" action available inline — no more hunting for which quota needs attention.
4. Search & Sort
A search bar lets you filter across quota names and resource types in real time. Within each group, quotas sort by usage percentage descending, so the most constrained resources bubble up automatically.
Preview
606403764-b2eca6d3-4308-48f2-a207-2b95a497ea70.mov
All reactions