Kubernetes Practical By Samson Tanimawo, PhD Published Dec 9, 2025 4 min read

ResourceQuota vs LimitRange

Both bound resources. Different scopes.

ResourceQuota

Total namespace resource cap. CPU, memory, pod count, PVC count.

Aggregate over all pods. Single namespace can't exceed allocation.

Use for: per-tenant capacity, per-environment capacity.

Per-pod or per-container default and max. Individual constraints.

Default values when pod spec is incomplete. Acts as a safety net.

Use for: prevent oversized pods, enforce reasonable defaults.

LimitRange first: sane per-pod defaults.

ResourceQuota second: namespace cap.

Together: pods are reasonable, and namespace can't exceed allocation.

Per-namespace ResourceQuota set at creation. IaC-managed.

Per-namespace LimitRange too. Standard template.

Quarterly: quotas vs actuals. Right-size; remove unused; expand for growing teams.