On-call notices a city API Pod is slow but still Running. Metrics show the container repeatedly hitting its CPU limit, while memory stays under the memory limit. What behavior should they expect from those limits?
Select an answer to reveal the explanation.
Short Explanation
CPU limits are like a speed governor — they hold you back but keep the engine running. Memory limits are a brick wall that can kill the process. Slow-but-alive often means throttle, not OOM.
Full Explanation
CPU limits constrain CFS quota and result in throttling when a container tries to use more CPU than allowed. Memory limits are hard caps enforced via cgroups; exceeding them can terminate the container with OOMKilled. Performance degradation under a CPU limit without restarts is consistent with throttling. Memory pressure past the limit produces a different failure mode.