In Kubernetes terms, cluster operators that want to restrictthe amount of resources a single container or pod may consume are able to define allowable ranges per Kubernetes namespace. In the absence of any explicit assignments, the Kubernetes systemis able to apply default resource limits and requests if desired in orderto constrain the amount of resource a pod consumes on a node.

By default,pods run with unbounded CPU and memory limits. This means that any pod in the system will be able to consume as much CPU and memory on the node that executes the pod.

Users may want to impose restrictions on the amount of resources a single pod in the system may consume for a variety of reasons. In general, users may:

• configure defaultmemory requests and limits for a namespace
• configure defaultCPU requests and limits for a namespace
• configure minimum and maximummemory constraints for a namespace
• configure minimum and maximumCPU constraints for a namespace
• configurememory and CPU quotas for a namespace
• configure apod quota for a namespace

Many thanksBoris Zaikin and Densify 🇨🇦 team for their contribution to community (Boris's article on Dev.tois here)! Canadian guys wrote some good examplesin the blog.

Photo by Glasscon of Germany.