A LimitRange in the reporting namespace sets max memory to 1Gi for…

Question

A LimitRange in the reporting namespace sets max memory to 1Gi for containers. A developer submits a Pod requesting 4Gi of memory. What is the expected result?

Accepted Answer

Admission rejects the Pod because the memory request exceeds the LimitRange maximum — LimitRange max is a per-container size check at the door. Ask for 4Gi when max is 1Gi and admission says no. The scheduler never gets a chance to “sort of” honor an oversized request.

Answer

The scheduler binds the Pod and kubelet silently caps memory at 1Gi

Answer

ResourceQuota automatically raises the namespace max to fit the 4Gi request

Answer

Only ClusterRoles can enforce LimitRange maxima; namespace LimitRanges are advisory

A LimitRange in the reporting namespace sets max memory to 1Gi for containers. A developer submits a Pod requesting 4Gi of memory. What is the expected result?

Short Explanation

Full Explanation