Skip to content

feat(quota): add display names and descriptions to compute quota limits#151

Merged
yahyafakhroji merged 1 commit into
mainfrom
feat/quota-limit-display-metadata
Jun 11, 2026
Merged

feat(quota): add display names and descriptions to compute quota limits#151
yahyafakhroji merged 1 commit into
mainfrom
feat/quota-limit-display-metadata

Conversation

@yahyafakhroji

Copy link
Copy Markdown
Contributor

What

Populate displayName + description on each spec.quota.limits[] entry in the compute ServiceConfiguration:

limit displayName
compute-workloads Workloads
compute-instances Instances
compute-vcpus vCPUs
compute-memory Memory

Why

The service-catalog quota fan-out generates a ResourceRegistration per limit. With these fields populated it stamps kubernetes.io/display-name / kubernetes.io/description, so portals (cloud-portal Quotas) render readable names instead of raw compute.datumapis.com/* metric keys.

⚠️ Depends on

milo-os/service-catalog#41 — adds DisplayName/Description to QuotaLimitSpec. This PR is draft until that lands and the ServiceConfiguration CRD with the new schema is deployed; applying before then would be rejected as unknown fields.

Related

Populate displayName/description on each spec.quota.limits[] entry so the
service-catalog quota fan-out stamps kubernetes.io/display-name and
kubernetes.io/description on the generated ResourceRegistrations. Portals
(cloud-portal Quotas) then render readable names (Instances, vCPUs, Memory,
Workloads) instead of raw compute.datumapis.com/* metric keys.

Requires the QuotaLimitSpec display fields from milo-os/service-catalog#41.
@yahyafakhroji yahyafakhroji self-assigned this Jun 11, 2026
@yahyafakhroji yahyafakhroji marked this pull request as ready for review June 11, 2026 01:13
@yahyafakhroji yahyafakhroji requested review from a team, kevwilliams and scotwells June 11, 2026 01:13
@yahyafakhroji yahyafakhroji merged commit 28508a0 into main Jun 11, 2026
9 checks passed
@yahyafakhroji yahyafakhroji deleted the feat/quota-limit-display-metadata branch June 11, 2026 10:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants