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

Support default k8s quotas properly #88

Open
jelkosz opened this issue Feb 6, 2023 · 0 comments
Open

Support default k8s quotas properly #88

jelkosz opened this issue Feb 6, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@jelkosz
Copy link
Contributor

jelkosz commented Feb 6, 2023

The current ClusterTemplateQuota defines the quota on either price/budget or on "num of cluster template instances" level. It can not define it on a level of "the user can use this amount of memory or CPU". This would not be particularly useful for clusters running in cloud, but very useful for the situation when the control plane is hypershift and the workers are kubevirt VMs running on the same cluster.
The ask here is NOT to re-implement the standard k8s quotas. The ask here is to:
1: make sure that when the standard k8s quotas are used, there is nothing standing in your way to use them to solve this use case
2: if the quota is violated, the appropriate errors are reported so that both the admin and the cluster creator can easily troubleshoot the problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants