Back to all scenarios
Scenario #40
Cluster Management
K8s v1.24, multi-tenant namespace setup
Cluster-Wide Crash Due to Misconfigured Resource Quotas
Cluster workloads failed after applying overly strict resource quotas that denied new pod creation.
Find this helpful?
What Happened
A new quota was applied with very low CPU/memory limits. All new pods across namespaces failed scheduling.
Diagnosis Steps
- 1Pod events showed failed quota check errors.
- 2Checked quota via kubectl describe quota in all namespaces.
Root Cause
Misconfigured CPU/memory limits set globally.
Fix/Workaround
• Rolled back the quota to previous values.
• Unblocked critical namespaces manually.Lessons Learned
Quota changes should be staged and validated.
How to Avoid
- 1Test new quotas in shadow or dry-run mode.
- 2Use automated checks before applying quotas.