By default, containers / pods are allocated unbound resources in the Kubernetes cluster. This allows them to consume as much resources as they need on a given node. However, this is a not a pretty scenario for cluster administrators. With the resource quotas, admins can restrict the amount of cpu and memory resources available, on a namespace basis. Within a namespace, the resource per container or pod can be controlled by using limit ranges.
Limit Range policy can be also be used to minimum and maximum storage request per PersistentVolumeClaim as well.
If no resource requests or limits are defined by the pod/container, limit range policy can be used to do the default allocation.
Read More »