exceeded quota Kubernetes Origin: Platform & cloud Last updated 15 Oct 2026

Error creating: pods is forbidden: exceeded quota: compute-resources, requested: limits.memory=1Gi, used: ..., limited: ...

The namespace’s ResourceQuota doesn’t have room for the new pod’s requests/limits (or object count).

Exact message you may see exceeded quotais forbidden: exceeded quota
Explore the map of this error Full error map →
Seen on: Kubernetes

Meaning

Quotas cap total CPU, memory, pods, PVCs or services per namespace. The ReplicaSet shows FailedCreate events with the numbers; pods are simply not created, so a Deployment looks stuck at fewer replicas.

Common causes

  • Namespace quota fully used
  • Pod requests/limits larger than needed
  • Old/completed pods or PVCs still counted
  • New replicas during rolling update temporarily exceed quota

⚡ Quick fix

  1. Inspect usage: kubectl describe quota -n ns
  2. Lower requests/limits or scale down other workloads
  3. Ask the cluster admin to raise the quota

Detailed fix by platform

Kubernetes

  1. bash
    kubectl describe resourcequota -n app
kubectl get events -n app --field-selector reason=FailedCreate

How to diagnose

  1. Quota — Used vs hard per resource
  2. Requests — Pod spec requests/limits
  3. Events — ReplicaSet FailedCreate

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):

402 — HTTP 402 Payment Required (HTTP)402Android resource linking failed — AAPT: error: resource x (aka y) not found — Android resource linking failed (Android)Android resource link…android:attr/lStar not found — AAPT: error: resource android:attr/lStar not found (Android)android:attr/lStar no…Duplicate resources — Execution failed for task ':app:mergeDebugResources'. > Duplicate resources (Android)Duplicate resourcesEvicted — Kubernetes: Pod Evicted — The node was low on resource: memory / ephemeral-storage (Kubernetes)EvictedFailedScheduling — Kubernetes: Pod stuck in Pending — FailedScheduling: 0/3 nodes are available (Kubernetes)FailedSchedulingmust specify limits — pods is forbidden: failed quota: must specify limits.cpu,limits.memory,requests.cpu,requests.memory (Kubernetes)must specify limitsResourceNotFound — ResourceNotFound: The Resource 'Microsoft.X/...' under resource group 'y' was not found (Azure)ResourceNotFoundexceeded …

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.