GKE Cluster Resource Quotas Overprovisioned
A quota set far above real usage stops being a guard: it neither prevents runaway consumption nor reflects what the namespace needs, so nobody can size the cluster from it.
Free to start. No card. The playground just needs your work email.
Google CloudKubernetes
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Reduce the GKE cluster's resource quotas. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.
- Applies to
- GKE Clusters on Google Cloud
- The fix, by hand
- List existing quotas: kubectl get resourcequota,limitrange --all-namespaces.
- For each tenant namespace, create a ResourceQuota: kubectl apply -f - under under under 'apiVersion: v1\nkind: ResourceQuota\nmetadata:\n name: default\n namespace: ‹ns›\nspec:\n hard:\n requests.cpu: "10"\n requests.memory: 20Gi\n limits.cpu: "20"\n limits.memory: 40Gi'.
- Add a LimitRange to enforce per-pod defaults + maxima so workloads without explicit requests still get a sensible floor.
- Watch Cloud Monitoring → kubernetes.io/container/cpu/limit_utilization for any namespace bumping the ceiling.
- Document the quota policy in the platform repo so application teams know the limits before deploying.
These are the steps the finding carries in the product.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1227- Full reference
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.