CONTAINERS / A CONCEPT NOTE
Resource Requests & Limits
sharing a node politely
Overview · mechanism
pitfall · examples
01 / THE SHORT VERSION
The idea in a few sentences.
Requests are the minimum CPU/Memory guaranteed to a container. Limits are the absolute maximum resources a container is permitted to consume before getting throttled or killed.
02 / FOLLOW THE MECHANISM
How resources conflicts occur
Request spec
pod specifies request: 1 CPU, 2GB RAM. Scheduler guarantees this capacity.
Spike activity
app consumes more CPU, crossing requests but staying under limits.
Memory Leak
container memory usage hits the hard limits boundary.
OOM Kill
orchestrator kills the container instantly with OOMKilled to protect node stability.
04 / COMMAND NOTES
Read the command, then the result.
Inspect the flags and arguments before trying an example. Snippets can need local setup, replacement values, or resources in your own environment.
view real-time CPU/Memory usage of active pods
kubectl top podsee resource allocations and allocations percentage
kubectl describe node NODE_NAME05 / CHECK YOURSELF
Could you explain Resource Requests & Limits to a teammate?
Try it out loud in two sentences: what it is, and the one detail that changes the picture. If you stall, the gap is the part to reread.
Up next in Containers & KubernetesNamespaces & Multi-tenancymany teams, one cluster