Code change:
This issue is meant to track planned work items for pre-allocated hugepages across releases. This issue captures the plan of record discussed in the wg-resource-mgmt meetings. [x] HugePages should be restricted via ResourceQuota [Owner: , fixed ] Assess ability to graduate feature to beta. [x] HugePages should require the user to request cpu or memory [Owner: fixed ] [x] HugePages should not be tied to QoS [Owner: fixed ] [ ] HugePages promoted to beta [Owner: ][ ] HugePages isolated at container and not just pod boundary [Owner: TBD] [ ] HugePages should be restricted via LimitRange [Owner: TBD] cc
/cc
If no one is doing it, I'd like to work on the ResourceQuota part.
would this be discussed in the meeting recently? i would like to try on the "via LimitRange" but seems more details need to be settled.
/cc
Regarding to the ResourceQuota issue, all I could think is to add support for resource HugePages in podEvaluator of quota, so that it could be aware of the hugepage declared in resourceQuota, and that requested in podSpec. It is thought to be a small change, The only thing that needs attention is the way to address resource HugePages, as it's name is not fixed, like CPU or memory, but in a specific format. Correct me if I miss something :)
-- the quota change is relatively small, if you want to pick up the work, i would be happy to shephard it.
-- you as owner, thanks for volunteering! let me know when you have the pr up
are you ready for the LimitRange part? :)
yes, I've worked on this for some time and will commit the pr ASAP.
/cc
hi, I am confused by the tests I've made, which seems the "HugePages should be restricted via LimitRange" has already been done. I created the LimitRange as below: apiVersion: v1 kind: LimitRange metadata: name: mytest spec: limits: default: hugepages-2Mi: 40Mi defaultRequest: hugepages-2Mi: 40Mi type: Container and the pods created by the following yaml: apiVersion: v1 kind: Pod metadata: generateName: hugepages-volume- spec: containers: image: tomcatjava:v6.0 command: name: example and the output of the pod in yaml is like: spec: containers: command: image: tomcatjava:v6.0 imagePullPolicy: IfNotPresent name: example resources: limits: hugepages-2Mi: 40Mi memory: 250Mi requests: hugepages-2Mi: 40Mi memory: 125Mi Is this the LimitRange part already been done? Otherwise anything wrong with my understanding? Also, I found an subtle error in the error info when creating pods restricted by the hugepage , would you please take a look?
-- thanks for the feedback, i have been distracted looking at other topics, but hope to return to this later this week.
I have filed an issue related to hugepages, would you please check when you are free? link:
you can't re-open an issue/PR unless you authored it or you are assigned to it. <detailsIn response to : /reopen </details
hi, I've worked on the HugePages isolated at container and not just pod boundary issue and would like to confirm some details. My first though was to implement this issue via docker, just like what cpu and memory did. But docker seems not support hugepage limit in present. Which means we have to get it done by coding in kubernetes or libcontainer, is that right? Please let me know if there are any other instructions that may help :)
-- to support isolation at container boundary, we would need support from the container runtime. that would require support in the CRI to expose the resource, and support in individual container runtimes (contianerd, cri-o, docker, rkt, etc.) to actually make use of it. in practice though, i have not seen a major requirement to support container boundary isolation. do you have use cases in mind that would require it?
I have no any other use cases as well, for now all the achievements fit well for our requirements. BTW, does the still need to move on? I found it seems already being supported by default.
I don't think the intent was for to close this /reopen
you can't re-open an issue/PR unless you authored it or you are assigned to it. <detailsIn response to : I don't think the intent was for to close this /reopen Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details

Related discussion:
text: CPUManager utilfeature.Feature = "CPUManager" // owner: @derekwaynecarr <del> // alpha: v1.8 </del> <ins> // beta: v1.10 </ins> // // Enable pods to consume pre-allocated huge pages of varying page sizes HugePages utilfeature.Feature = "HugePages"