apiserver-resourcequota.v1.md

title	content_type	package	auto_generated
kube-apiserver ResourceQuota Configuration (v1)	tool-reference	apiserver.config.k8s.io/v1	true

Package v1 is the v1 version of the API.

Resource Types

• Configuration

Configuration {#apiserver-config-k8s-io-v1-Configuration}

Configuration provides configuration for the ResourceQuota admission controller.

Field	Description
apiVersion string	apiserver.config.k8s.io/v1
kind string	Configuration
limitedResources []LimitedResource	LimitedResources whose consumption is limited by default.

LimitedResource {#apiserver-config-k8s-io-v1-LimitedResource}

Appears in:

• Configuration

LimitedResource matches a resource whose consumption is limited by default. To consume the resource, there must exist an associated quota that limits its consumption.

Field	Description
apiGroup string	APIGroup is the name of the APIGroup that contains the limited resource.
resource [Required] string	Resource is the name of the resource this rule applies to. For example, if the administrator wants to limit consumption of a storage resource associated with persistent volume claims, the value would be "persistentvolumeclaims".
matchContains [Required] []string	For each intercepted request, the quota system will evaluate its resource usage. It will iterate through each resource consumed and if the resource contains any substring in this listing, the quota system will ensure that there is a covering quota. In the absence of a covering quota, the quota system will deny the request. For example, if an administrator wants to globally enforce that that a quota must exist to consume persistent volume claims associated with any storage class, the list would include ".storageclass.storage.k8s.io/requests.storage"
matchScopes []core/v1.ScopedResourceSelectorRequirement	For each intercepted request, the quota system will figure out if the input object satisfies a scope which is present in this listing, then quota system will ensure that there is a covering quota. In the absence of a covering quota, the quota system will deny the request. For example, if an administrator wants to globally enforce that a quota must exist to create a pod with "cluster-services" priorityclass the list would include "scopeName=PriorityClass, Operator=In, Value=cluster-services"