Building-permits developers notice pods consume more CPU and memory than their manifests declare. A LimitRange applies default requests and limits in the namespace. What is the most accurate explanation?
Select an answer to reveal the explanation.
Short Explanation
If the YAML looks skinny but the scheduler sees a heavier ask, a LimitRange probably stamped defaults at admission. The cluster fills in what the developer left blank.
Full Explanation
LimitRange can mutate pods at admission to set default requests and limits when the pod spec omits them. Those defaults become the values used for scheduling and accounting, so observed consumption and reservation can exceed what authors expected from the raw manifest. kubectl top scaling myths, PVC-to-CPU coupling, and NetworkPolicy-driven QoS changes are not how LimitRange works.