Container has no CPU limit Affecting Deployment service in Kubernetes
Severity Framework
CCSS (Common Configuration Scoring System) is a set of measures used to determine the severity of the rule.
Snyk CCSS
Rule category
Each rule is associated with a high-level category. For example IAM, Container, Monitoring, Logging, Network, etc.
Containers/ Best Practices
Is your environment affected by this misconfiguration?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsFrameworks
CIS-ControlsCSA-CCM
- Snyk IDSNYK-CC-00609
- creditSnyk Research Team
Description
CPU limits can prevent containers from consuming valuable compute time for no benefit (e.g. inefficient code) that might lead to unnecessary costs. It is advisable to also configure CPU requests to ensure application stability.
How to fix?
Add resources.limits.cpu field with required CPU limit value.
Add resources.limits.cpu field with required CPU limit value.
Example Configuration
resource "kubernetes_pod" "allowed" {
metadata {
name = "terraform-example609a"
}
spec {
container {
resources {
limits = {
memory = "512Mi"
cpu = "500m"
}
}
image = "nginx:1.7.9"
name = "example"
}
}
}