kubernetes

Kubernetes Resource Quota Calculator

Calculate namespace ResourceQuota values for your Kubernetes cluster. Set CPU and memory limits per namespace based on team size, pod count, and a safety buffer.

Kubernetes Resource Quotas for Multi-Team Clusters

ResourceQuota prevents any single team or workload from consuming all cluster resources. It's essential in shared Kubernetes clusters.

ResourceQuota YAML

yaml

apiVersion: v1
kind: ResourceQuota
metadata:
  name: team-quota
  namespace: team-alpha
spec:
  hard:
    requests.cpu: "5"          # from calculator
    requests.memory: "10Gi"    # from calculator
    limits.cpu: "10"
    limits.memory: "20Gi"
    count/pods: "20"
    count/services: "10"
    count/persistentvolumeclaims: "5"

LimitRange for Defaults

yaml

apiVersion: v1
kind: LimitRange
metadata:
  name: default-limits
  namespace: team-alpha
spec:
  limits:
    - type: Container
      default:
        cpu: 500m
        memory: 256Mi
      defaultRequest:
        cpu: 100m
        memory: 128Mi
      max:
        cpu: "4"
        memory: 8Gi

Multi-Namespace Strategy

Team Type	Buffer	Quota Strategy
Production	20–30%	Quota on requests + limits
Staging	10–20%	Quota on requests only
Development	30–50%	Loose quota + LimitRange defaults

Monitoring Quota Usage

bash

kubectl describe resourcequota -n team-alpha
kubectl get resourcequota --all-namespaces

Key Terms

Full glossary →

kubeadm

A tool for bootstrapping Kubernetes clusters. It automates the setup of control plane components and joining worker nodes, following Kubernetes best practices.

etcd

A distributed key-value store used by Kubernetes to store all cluster state and configuration. etcd is the single source of truth for the entire cluster.

cert-manager

A Kubernetes controller for automating TLS certificate management. cert-manager can issue certificates from Let's Encrypt, Vault, or internal CAs, and automatically renews them.

Helm

A package manager for Kubernetes. Helm charts bundle Kubernetes manifests into reusable packages with configurable values, versioned and published to chart repositories.

Frequently Asked Questions

What is a ResourceQuota and why use one?

A ResourceQuota caps the total CPU, memory, and object counts that can be consumed by all Pods in a namespace. Without quotas in a multi-team cluster, one team's runaway job can starve other teams of resources. Quotas enforce fair sharing and prevent accidental resource exhaustion.

Should I set requests or limits in ResourceQuota?

Always quota requests (requests.cpu, requests.memory) rather than limits. Limits are optional on Pods and hard to predict. Quotas on requests give a fair representation of reserved capacity. If you also quota limits, every Pod must have a limit set — this enforces LimitRange usage.

What happens when a namespace hits its quota?

New Pod creations fail with a 403 'exceeded quota' error. Running Pods are not evicted — only new scheduling is blocked. This is why the burst buffer matters: without it, a legitimate scaling event will fail. Set the buffer to at least your HPA max-replicas overhead.

How do ResourceQuota and LimitRange work together?

ResourceQuota caps total namespace usage. LimitRange sets default and maximum request/limit per individual Pod. Together: LimitRange ensures every Pod has sensible defaults (so Pods without explicit requests count against the quota), while ResourceQuota caps the namespace total. Use both in production multi-tenant clusters.

Related Tools

K8s Node Sizing

Calculate the right number and size of Kubernetes worker nodes for your workloads. Supports Hetzner Cloud and Vultr with verified pricing.

HPA Thresholds

Calculate the right HPA (Horizontal Pod Autoscaler) CPU and memory thresholds for your Kubernetes workloads. Get absolute target values in millicores and MiB.

K8s Cluster Cost

Calculate the monthly cost of running a Kubernetes cluster on Hetzner Cloud. Choose server types for control planes, workers, and load balancers with HA mode.

Related Guides