How to fix etcd quota exceeded, event limit reached, API server rejecting requests in Kubernetes
KubernetesADVANCEDCRITICAL
etcd database full with Kubernetes events. Fix by cleaning up old events, increasing quota, or using separate etcd for events.
What this error means
Kubernetes events can consume most of etcd storage, causing the cluster to reach quota and rejecting new writes.
Typical symptoms
- Cluster becomes read-only
- New resource creation fails
- etcd database very large
- API server errors about quota
Common causes
- Too many events generated
- Event cleanup/TTL not configured
- etcd quota too small
- No automatic event cleanup
How to fix "etcd quota exceeded, event limit reached, API server rejecting requests"
kubectl exec -n kube-system etcd-<node> -- etcdctl endpoint status
kubectl delete events --all -A
Add --quota-backend-bytes flag to etcd.
Set --event-ttl=1h on API server.
Advanced notes
Consider dedicated etcd instance for events.
Official resources & further reading