Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: refactor quotas #1251

Open
oliverbaehler opened this issue Nov 20, 2024 · 1 comment
Open

feat: refactor quotas #1251

oliverbaehler opened this issue Nov 20, 2024 · 1 comment
Labels
blocked-needs-validation Issue need triage and validation needs-discussion No outline on the feature, discussion is welcome

Comments

@oliverbaehler
Copy link
Collaborator

Describe the feature

Currently via the Tenant specification we can create quotas, which are scoped to the entire tenant or for each namespace identical. I would like to remove the spec or deprecate it in favour of different approaches.

  • Add a new CRD called GlobalQuota, the Quota has a namespace selector as property, allowing to select all namespaces within a tenant or select from multiple tenants. The CRD would track the usage in their status, which is currently doe via annotations. Seems like a much cleaner approach. Additionally it should have a webhook, checking all resources which can allocate ifra resources (Pods and PVs) if the requested resources go over that status threshold.

  • Namespace-scope can be covered via Replications, therefor nothing new to implement

I would completely remove the quota spec with the v1 release, WDYT @prometherion @MaxFedotov

@oliverbaehler oliverbaehler added the blocked-needs-validation Issue need triage and validation label Nov 20, 2024
@prometherion
Copy link
Member

I'm ok with that, what I'm worried about is that we should replicate all the ResourceQuota behaviours and scopes, which is not easy.

@prometherion prometherion added the needs-discussion No outline on the feature, discussion is welcome label Dec 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked-needs-validation Issue need triage and validation needs-discussion No outline on the feature, discussion is welcome
Projects
None yet
Development

No branches or pull requests

2 participants