Skip to main content

KA-B001: Missing CPU requests

Warning Best Practice

Why This Matters

The container does not define a CPU request. Without CPU requests, the Kubernetes scheduler cannot make informed placement decisions. The container falls into the BestEffort QoS class and will be the first to be evicted under node memory pressure.

How to Fix

Add a CPU request to the container resources

Before (incorrect)

containers:
  - name: app
    image: myapp:1.0

After (correct)

containers:
  - name: app
    image: myapp:1.0
    resources:
      requests:
        cpu: 100m

Rule Details

Rule Code
KA-B001
Severity
Warning
Category
Best Practice

Related Rules

KA-B002 Warning

Missing CPU limits
KA-B003 Warning

Missing memory requests
KA-B004 Warning

Missing memory limits
KA-B009 Warning

Liveness probe port not in container ports
KA-B010 Warning

Readiness probe port not in container ports