Kubernetes uses ResourceQuota and LimitRange objects to manage how workloads consume cluster resources. Understanding how these objects differ helps you control resource usage at both the namespace and pod level.

ResourceQuota

A ResourceQuota object limits the total amount of resources that all workloads in a namespace can use. It helps you prevent teams or applications from consuming more than their fair share of CPU, memory, GPU, or other resources.

If creating or updating a workload would exceed a quota, Kubernetes blocks the request and returns an HTTP 403 status code. You can view the related messages using:

kubectl get events

LimitRange

A LimitRange defines the minimum and maximum compute resources a pod or container can request and use. It ensures that workloads in a namespace follow consistent request and limit values.

LimitRange helps you:

• Apply default CPU and memory requests

• Apply default limits

• Prevent workloads from exceeding allowed per‑object settings

How ResourceQuota and LimitRange work together

• ResourceQuota manages total consumption for the entire namespace.

• LimitRange manages per‑pod and per‑container constraints within that namespace.

Using both objects together helps you keep namespaces predictable, enforce guardrails, and prevent workloads from over‑allocating resources.