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

**Code:** `exceeded quota` · **Category:** Kubernetes · **Seen on:** Kubernetes

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

## 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

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/kubernetes/exceeded-quota)