Kubernetes Resource Quota Calculator

CPU request is the amount of CPU guaranteed to your container — the scheduler uses this to place pods on nodes. CPU limit is the maximum CPU a container can use before being throttled. Limits can be higher than requests to allow bursting. If a container exceeds its CPU limit, it is throttled (not killed).

Unlike CPU throttling, exceeding the memory limit causes the container to be OOMKilled (Out of Memory killed) and restarted. Always set memory limits conservatively and monitor actual usage with kubectl top or Prometheus.

ResourceQuota sets aggregate limits on total resource consumption across all pods in a namespace. LimitRange sets default request/limit values on individual containers when none are specified in the pod spec. Use both together: ResourceQuota to cap total namespace usage, LimitRange to ensure all containers have sensible defaults.

CPU is specified in cores (1, 0.5) or millicores (500m = 0.5 cores, 100m = 0.1 cores). Memory uses binary suffixes: Ki (kibibytes), Mi (mebibytes), Gi (gibibytes). Always prefer binary units (Mi, Gi) over decimal (M, G) to avoid ambiguity.

Copy the generated YAML and run: kubectl apply -f quota.yaml -n <namespace>. To view current usage: kubectl describe resourcequota -n <namespace>.