Rightsizing Kubernetes requests/Limits usage

tjtharrison
7 min readJan 13, 2024

At the end of last year, I started seeing this error pop up on occasion when I deploy a new deployment into my cluster — So thought this was a good opportunity to do some house keeping.

Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedScheduling 4m33s default-scheduler 0/3 nodes are available: 3 Insufficient cpu. preemption: 0/3 nodes are available: 3 No preemption victims found for incoming pod..
Warning…

--

--