CPU Over-Provisioned
A container's CPU request is reserved on its node and counts against what the scheduler can place there, so a request well above real use holds capacity away from other workloads.
Free to start. No card. The playground just needs your work email.
AWSAzureGoogle CloudKubernetes
Found, explained, handed over.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across AWS, Azure and Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Reduce the CPU request on deployment. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
The finding opens with the change already spelled out, so the fix is one ticket, not an investigation.
- Applies to
- EKS Deployments on AWS, EKS StatefulSets on AWS, AKS Deployments on Azure, AKS StatefulSets on Azure, GKE Deployments on Google Cloud, GKE StatefulSets on Google Cloud
- 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 IDs
RC-1770RC-1771RC-1870RC-1871RC-1970RC-1971- 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.