Every pod carries a CPU meter and a memory meter: a blue tick for its request, a bright cap for its limit, a fill for what it uses. Burst, spike, leak, or add a big pod, and watch the node respond. Or press ▶ Guided tour.
| Pod | QoS class | CPU req / lim / use | Mem GiB req / lim / use | Restarts | State |
|---|
Requests are what the scheduler reserves on a node; it places a pod only where the sum of requests still fits, so a big pod can stay Pending on an idle node. Limits cap a running container: CPU above the limit is throttled, memory above the limit gets the container OOM-killed and restarted. Requests and limits set the QoS class (Guaranteed, Burstable, BestEffort), and under memory pressure the kubelet evicts BestEffort pods first.