0
0

Cloud Manager Reference Manual

Docs
Docs EInnovator Posted 13 May 20

Cloud Manager » Quotas

Kubernetes allows cluster administrators to limited the maximum amount of resources each Space/Namespace is allowed to allocated. This is done by defining (Resource) Quotas in a Space/Namespace. A Quota object allows to fine-grain limits on each individual type of resource (e.g. Memory, CPU, Storage, Pod count, etc.). CloudManager provider a simplified UI for administrators to edit Quotas, and for developers to check current level of resource usage.

About Quotas

A Quota object allows to fine-grain limits on each individual type of resource. A quota policy for a Space can be defined by multiple policies, but a single Quota is enough for many use cases as it allows to defined a limit per object type. In CloudManager the Quota object for a Space (if a single one), is usually named quota as this is the default name selected by CloudManager.

Table below summaries the types of resources that a Quota can specify limits.

ResourceK8s KeyLimit Type/UnitDescription
MemorymemoryGiLimit to total Memory allocated by Pods in the Space
CPUcpu Limit to total CPUs allocated by Pods in the Space
Storagerequests.storageGiLimit to total Storage allocated by PersistentVolumeClaims in the Space
Storageephemeralrequests.ephemeral-storageGiLimit to total Ephemeral Storage allocated by Pods in the Space
Podscount/podsint counterLimit to total count of non-terminal Pods (not Failed or Succeeded) in the Space
Deploymentscount/deployments.appsint counterLimit to total count of Deployments in the Space
Deployment Exts.count/deployments.extensionsint counterLimit to total count of DeploymentExtensions in the Space
ReplicaSetscount/replicasets.appsint counterLimit to total count of ReplicaSets in the Space
Replication Controllerscount/replicationcontrollersint counterLimit to total count of ReplicationControllers in the Space
StatefulSetscount/statefulsets.appsint counterLimit to total count of StatefulSets in the Space
Jobscount/jobs.batchint counterLimit to total count of Jobs in the Space
CronJobscount/cronjobs.batchint counterLimit to total count of CronJobs in the Space
Servicescount/servicesint counterLimit to total count of Services in the Space
Load-Balancerscount/service.loadbalancersint counterLimit to total count of Services of type LoadBalancer in the Space
NodePortscount/service.nodeportsint counterLimit to total count of Services of type NodePort in the Space
ConfigMapscount/configmapsint counterLimit to total count of ConfigMaps in the Space
Secretscount/secretsint counterLimit to total count of Secrets in the Space
VolumeClaimscount/persistentvolumeclaimsint counterLimit to total count of PersistentVolumeClaims in the Space
Quotascount/resourcequotasint counterLimit to total count of ResourceQuotas in the Space

Browsing Space Quotas

An administrator may defined one (or more) Quota to limit the maximum amount of resources each Space is allowed to allovate. The tab Settings > Quotas space dashboard page, display the list of Quota setup for the Space, the detailed settings of a Quota object, and current usage in absolute values and in percentage meters.

Percentage meters color vary with level of usage as follow:

  • (green) — 0% ≤ usage ≤ 75%
  • (orange) — 75% ≤ usage < 90%
  • (red) — 90% ≤ usage ≤ 100%

Image below show an example of a cluster listing.

Quotas

Editing Space Quotas [Admin]

Users authorized to administrate a Cluster can set Quotas for new Spaces/Namespaces created in that cluster. The tab Settings > Quotas space dashboard page, displays the list of Quota setup for the Space and the settings of for each type of resource for the selected quota.

When new quota values are edited and saved, and no Quota currently existing or is selected, a new Quota quota object named quota is automatically created by CloudManager. To help selecting appropriate values, the current resource usage is also shown in absolute values and in percentage meters.

Updates to Quota setting do not affect objects in the Space that already exist. For example, if the current Pod count is 55, and the the limit on the count is changed from 100 to 50, the existing Pods are not affected – but no new Pods can be created in the Space until the current number is below 50 or the Quota settings are changed again.

Image below show an example of a Quotas being edit by the administrator:

Edit Quotas

Cluster Settings for Default Quotas

Users authorized to administrate a Cluster can also set default limits and Quotas for new Spaces created in the **Cluster. If so, all new Spaces created in the Cluster using the CloudManager (UI or API) will have an initial Quota named quota automatically created and configured with values taken form the default settings. After the Space is created, changes to the default limits no longer affect the Space limits.

Image below shows the UI to set cluster-wide default settings for the Quota to apply to a space when is created.

Cluster Environemnt

Learning More

Comments and Discussion

Content