Skip to content

feat(quota): add display name/description to the billing-accounts quota limit#59

Open
yahyafakhroji wants to merge 1 commit into
mainfrom
feat/quota-limit-display-metadata
Open

feat(quota): add display name/description to the billing-accounts quota limit#59
yahyafakhroji wants to merge 1 commit into
mainfrom
feat/quota-limit-display-metadata

Conversation

@yahyafakhroji

Copy link
Copy Markdown

What

Add displayName: Billing Accounts + a description to the billing-accounts-per-organization entry under spec.quota.limits in the billing ServiceConfiguration.

Why

The service-catalog quota fan-out builds the billing.miloapis.com/billingaccount/count ResourceRegistration from the limit (not the metric). With these fields set it stamps kubernetes.io/display-name / kubernetes.io/description, so portals (cloud-portal Quotas) render "Billing Accounts" instead of the raw metric key. The metric already carried a display name; this brings the quota limit to parity.

⚠️ Deploy ordering

Depends on milo-os/service-catalog#41 (adds DisplayName/Description to QuotaLimitSpec), now merged. This should be rolled out after a service-catalog build containing #41 is deployed — applying the new fields against an older CRD would be rejected as unknown fields.

Related

… quota limit

Populate displayName/description on the billing-accounts-per-organization
quota limit so the service-catalog quota fan-out stamps
kubernetes.io/display-name and kubernetes.io/description on the generated
billing.miloapis.com/billingaccount/count ResourceRegistration. Portals
(cloud-portal Quotas) then render "Billing Accounts" instead of the raw
metric key.

Requires the QuotaLimitSpec display fields from milo-os/service-catalog#41.
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.

1 participant