DevOps Glossary

Kubernetes LimitRange is a namespace-scoped Kubernetes policy that sets default, minimum, and maximum resource values for pods, containers, and persistent volume claims at admission time. It helps platform teams prevent workloads from running without CPU or memory settings, requesting too much capacity, or using storage outside allowed bounds. A LimitRange can apply default CPU and memory requests or limits, enforce min and max values, and control request-to-limit ratios, such as requiring a container’s memory limit to stay within 2x of its request. For example, a development namespace might default each container to a 250m CPU request and 512Mi memory limit, while rejecting any container that asks for more than 2 CPUs or 4Gi of memory. LimitRange works well with ResourceQuota: LimitRange controls per-object values, while ResourceQuota caps total namespace usage. It is useful in shared clusters, managed platforms such as Azure Kubernetes Service, and production environments where teams need clear guardrails without editing every workload manifest by hand.