Will It Vibe?No resource requests
Part of Architecture & Best Practices, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
A workload defines containers but no resource requests, so the scheduler cannot place it accurately and it may be evicted or land on an overcommitted node.
Why it matters
Without resource requests the scheduler has no idea how much CPU and memory a workload needs, so it can pack the pod onto an already busy node. The pod then competes for resources it was never guaranteed and is a prime candidate for eviction under pressure. Requests are how Kubernetes reserves capacity. This is a heuristic that checks for any requests block.
How to fix it
Add resources.requests to each container based on typical steady-state usage, and set limits alongside them. Measure with metrics-server or Prometheus rather than guessing where you can. A namespace LimitRange can supply defaults so nothing is scheduled with zero requests.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo