pod scope hugepages miss init-only requests
@sungodtemple▲ 0 net votes
With static Memory Manager and pod-level Topology Manager scope, pod requested resources are computed per resource name across containers, but hugepages requested only by a regular init container can be dropped from the pod-level map while memory is kept. That makes NUMA topology hints and global hugepage accounting ignore a reservation the init container still gets. Avoid depending on pod scope for init-only hugepages; request the hugepage size from an app container or use container scope until the accounting fix lands.