Account quotas are like Kubernetes resource quotas but they are aggregated across namespaces, i.e. if you specify a limit such as
limits.memory: 8Gi, the user can use up to 8Gi of memory across all the spaces owned by the account that the quota is defined for.
Admins can manage account quotas in the "Quotas" tab of each cluster. Users can view a list of all quotas of their accounts as well as of the quotas of the accounts of their teams under "Quotas". Both views also show the current utilization for each quota limit.
Account quotas can be created for any existing cluster account and as part of the process of updating and creating cluster accounts when using the UI.
Restrict Resource Amounts (e.g. virtual clusters, pods)
One common use case for account quotas is to restrict the amount of virtual clusters a user can create. This can be done by using the object count quota as in a regular resource quota.
With this you can limit any account to a specific amount of objects, such as
virtualclusters and others.
For example, if you want to restrict a user to only create up to 2 virtual clusters through Loft, you can define:
Select the account this quota should apply to and enter in the quota section:
The press 'Create' to apply the quota.
Namespace Scoped Resources
Resource and account quotas can only restrict namespaced resources, such as pods, deployments etc. If you want to restrict the amount of spaces a user can create, please take a look at the account space creation settings