Shulou(Shulou.com)06/01 Report--

This article shows you the overview of ResourceQuota in the design and implementation of Kubernetes, which is concise and easy to understand, which will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

ResourceQuota is an object provided by Kubernetes to limit resource quotas. Cluster administrators can create ResourceQuota objects for each namespace to limit the maximum usage of specific types of resources, so that cluster resources can be allocated more accurately and reasonably and prevent resources in multiple namespace from competing for shared cluster resources.

The background of ResourceQuota

In practical application scenarios, multiple users or teams often share the same cluster. Administrators often assign different namespace to different users or teams, thus isolating each other, but namespace can only be logically isolated. Applications in multiple namespace will still share the hardware resources of the cluster, such as CPU, memory and storage. If an application under a namespace consumes these shared resources Then it is bound to affect other applications under namespace.

ResourceQuota provides a solution to this problem. For example, if user An and B share a cluster with 16-core CPU and 32 GB of memory resources, and user An and B use namespace-an and namespace-b respectively, the administrator can create a ResourceQuota object in namespace-an and namespace-b, and specify a CPU and memory quota (such as sharing cluster resources equally). Then the total consumption of application resources created by user An and B will not exceed this quota. Kubernetes will refuse to create new applications.

ResourceQuota feature enabled

To enable the ResourceQuota feature, you need to add the string "ResourceQuota" to the-- enable-admission-plugins parameter list in kube-apiserver. For example:

# kube-apiserver-enable-admission-plugins= "ResourceQuota,"

In most Kubernetes distributions, ResourceQuota is enabled by default.

ResourceQuota resource configuration

A simple ResourceQuota configuration, as follows:

ApiVersion: v1kind: ResourceQuotametadata: name: pod-count namespace: defaultspec: hard: pods: "0"

This configuration will create a ResourceQuota object in the namespace named default, which will ensure that the creation of the Pod object is "prohibited" in that namespace. Its main configuration is as follows:

The namespace to which the metadata.namespace:ResourceQuota object belongs, which is also the namespace of the object

Spec.hard: specify a list of hard quotas

Spec.hard.pods: sets a quota for the number of Pod objects

ResourceQuota also supports other richer configurations, such as resource quotas for feature status, resource quotas for specific priorities, and so on, which we will cover in later chapters.

Resources that ResourceQuota can limit

ResourceQuota supports setting limits for multiple types of resources:

Computing resources, such as CPU, memory, etc.

Extend class resources, such as GPU

Storage resources, such as persistent volumes

In addition to these resource types, it also supports limiting the number of objects, including:

Configmaps

Persistentvolumeclaims

Pods

Replicationcontrollers

Resourcequotas

Services

Services.loadbalancers

Services.nodeports

Secrets

The above is an overview of ResourceQuota in the design and implementation of Kubernetes. Have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.