A team wants to omit memory limits on a bursty reporting container…

Question

A team wants to omit memory limits on a bursty reporting container so it can use spare node memory. What risk must they accept?

Accepted Answer

Without a memory limit, the container can consume unbounded memory and create noisy-neighbor pressure or OOM conditions on the node. — No memory limit is an open bar—great until one guest drains the keg. The app can burst into spare RAM, but it can also starve neighbors or trigger node OOM. Know that tradeoff before you skip limits.

Answer

Omitting limits automatically converts the Pod to Guaranteed QoS and pins it to a single CPU.

Answer

The kubelet will refuse to start any container that lacks a memory limit in every namespace.

Answer

Services will stop load-balancing to Pods that have requests but no limits.

A team wants to omit memory limits on a bursty reporting container so it can use spare node memory. What risk must they accept?

Short Explanation

Full Explanation