Add support for pre-allocated hugepages

[derekwaynecarr]

Feature Description

• One-line feature description (can be used as a release note): Enable a pod to express a resource requirement for a pre-allocated hugepage of a particular size. Kubelet isolates access to hugepages.
• Primary contact (assignee): @derekwaynecarr
• Responsible SIGs: sig-node
• Design proposal link (community repo): HugePages proposal community#837
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @vishh @sjenning
• Approver (likely from SIG/area to which feature belongs):
• Initial target stage (alpha/beta/stable) and release (x.y): alpha release 1.8, beta 1.10

[idvoretskyi]

@derekwaynecarr which stage does this feature target - alpha, beta or stable for 1.7?

[vishh]

Per offline discussions, design review is what is planned for v1.7.

…

On Wed, May 3, 2017 at 1:49 PM, Ihor Dvoretskyi ***@***.***> wrote: @derekwaynecarr <https://github.com/derekwaynecarr> which stage does this feature target - alpha, beta or stable for 1.7? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#275 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGvIKMI-lHsTIyL2Ge0_0yrRy60Tm2_aks5r2Oh3gaJpZM4NIEeu> .

[calebamiles]

Moving this feature to the 1.8 milestone for implementation, @derekwaynecarr, @vishh.

cc: @dchen1107, @idvoretskyi, @kubernetes/kubernetes-release-managers, @kubernetes/sig-node-feature-requests

[derekwaynecarr]

@calebamiles -- i had updated the description text last week but forgot to update the label for 1.8, updated now as this is being done via sig-node.