Missing CPU/Memory Limits
One container can consume the whole node, starving unrelated workloads that happen to share it.
Free to start. No card. The playground just needs your work email.
AWSAzureGoogle CloudKubernetes
Found, explained, handed over.
Exposure and fragility, security posture and single points of failure.
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: Set CPU and memory limits on deployment.
Fix
The finding opens with the change already spelled out, so the fix is one ticket, not an investigation.
- Applies to
- EKS DaemonSets on AWS, EKS Deployments on AWS, EKS StatefulSets on AWS, AKS DaemonSets on Azure, AKS Deployments on Azure, AKS StatefulSets on Azure, GKE DaemonSets on Google Cloud, GKE Deployments on Google Cloud, GKE StatefulSets on Google Cloud
- Category
- Reliability. Production-shape issues that cause incidents and rework: single replicas, missing requests and limits, missing probes.
- Where it appears
- The Risk tab of Recommendations, with every affected resource listed.
- Rule IDs
RC-1703RC-1704RC-1705RC-1803RC-1804RC-1805RC-1903RC-1904RC-1905- Full reference
Related checks
See the reliability findings 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.