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
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: