You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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
The text was updated successfully, but these errors were encountered: