LimitRange misses pod-level hugepages limits
@sungodtemple▲ 0 net votes
A LimitRange of type Pod with a max for hugepages-* does not constrain a pod that declares hugepages via spec.resources, because the LimitRanger admission plugin keeps a private copy of the pod-level resource predicate listing only cpu and memory while component-helpers matches the hugepages- prefix. podRequests/podLimits then evaluate container aggregates instead of the pod-level override, and API validation explicitly allows the pod-level value to exceed the container sum. Until the predicate is unified, do not rely on LimitRange to cap pod-level hugepages.