Add downward API support for hugepages

[derekwaynecarr]

Enhancement Description

• One-line enhancement description (can be used as a release note): Add downward API support for hugepages
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/2053-downward-api-hugepages
• Discussion Link: https://docs.google.com/document/d/1Ne57gvidMEWXR70OxxnRkYquAoMpt56o75oZtg-OeBg/edit?disco=AAAAG5bcPuM
• Primary contact (assignee): @derekwaynecarr
• Responsible SIGs: sig-node
• Kubernetes PR: https://github.com/kubernetes/kubernetes/pull/86102
• k/website PR: https://github.com/kubernetes/website/pull/24904
• Enhancement target (which target equals to which milestone):
  • [x] Alpha release target 1.20
  • [x] Beta release target 1.21
  • [x] Stable release target 1.27:
    • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/3719
    • [ ] Code (k/k) update PR(s):
    • [ ] Docs (k/website) update(s):

[derekwaynecarr]

After reflecting on the implementation PR: https://github.com/kubernetes/kubernetes/pull/86102

I think this needs a KEP as it loosens validation, and as a result, the feature requires that all kubelets have the support enabled before the API server accepts its usage. Will write a quick KEP now.

/sig node

[kikisdeliveryservice]

Took a quick :eyes: and the kep would need alpha graduation criteria but other than that it has the testplans, implementable state, etc... So would need that update and to merge before October 6th

[kikisdeliveryservice]

PR https://github.com/kubernetes/enhancements/pull/2055 was updated and now it meets the criteria (pending sig-node review ofc), we'll just need this to merge by October 6th to be included in 1.20

[kinarashah]

Hi @derekwaynecarr,

Enhancement shadow for 1.20 release team here 👋 ,

Just a reminder that the Enhancements Freeze is Tomorrow October 6th EOD PST. All KEPs and updates must be merged by that time. After October 6th, you will need to request an Exception to be included in the 1.20 Release.

Thank you.

[kinarashah]

Hi @derekwaynecarr ,

Since your Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates: Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline Thursday, Nov 12th: Week 9 - Code Freeze

As a reminder, please link all of your k/k PR as well as docs PR to this issue so we can track them.

Thank you!

[annajung]

Hello @derekwaynecarr 👋 , 1.20 Docs lead here.

Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?

If so, please follows the steps here to open a PR against dev-1.20 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Nov 6th

Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

[annajung]

Hi @derekwaynecarr

The docs placeholder deadline is this Friday. Please make sure to create a placeholder PR against the dev-1.20 branch in the k/website before the deadline

Also, please keep in mind the important upcoming dates:

• Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
• Thursday, Nov 12th: Week 9 - Code Freeze
• Monday, Nov 23rd: Week 11 - Docs PR Ready for Review

As a reminder, please link all of your k/k PR as well as docs PR to this issue for the release team to track.

[derekwaynecarr]

@annajung placeholder pr is https://github.com/kubernetes/website/pull/24904

[kikisdeliveryservice]

Hey @derekwaynecarr

it looks like all the k/k prs for this have merged, correct?

Thanks! Kirsten

[kikisdeliveryservice]

Confirmed with Derek that this is completed for code freeze.

[derekwaynecarr]

/milestone v1.21

[annajung]

Hi @derekwaynecarr

Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:

• Tuesday, March 9th: Week 9 - Code Freeze
• Tuesday, March 16th: Week 10 - Docs Placeholder PR deadline
  • If this enhancement requires new docs or modification to existing docs, please follow the steps in the Open a placeholder PR doc to open a PR against k/website repo.

As a reminder, please link all of your k/k PR(s) and k/website PR(s) to this issue so we can track them.

Thanks!

[annajung]

Hi @derekwaynecarr

Enhancements team is marking this enhancement as "At Risk" for the upcoming code freeze due to not seeing any linked k/k PR(s) for this enhancement.

Please make sure to provide all k/k PR(s) and k/website PR(s) to this issue so it can be tracked by the release team.

[sjenning]

e2e test for this https://github.com/kubernetes/kubernetes/pull/99612

[annajung]

Hey @derekwaynecarr

A friendly reminder that Code freeze is 5 days away, March 9th EOD PST

Enhancements team is currently tracking the following PR(s):

• https://github.com/kubernetes/kubernetes/pull/99610
• https://github.com/kubernetes/kubernetes/pull/99612

Any enhancements that are NOT code complete by the freeze will be removed from the milestone and will require an exception to be added back.

Please also keep in mind that if this enhancement requires new docs or modification to existing docs, you'll need to follow the steps in the Open a placeholder PR doc to open a PR against k/website repo by March 16th EOD PST

Thanks!

[annajung]

Hi @derekwaynecarr, with the two PRs merged, I am marking this as code complete for the release. If there are any other PRs that should be tracked, please let me know. Thanks!

[reylejano]

Hello @derekwaynecarr, 1.21 Docs lead here. Does this enhancement work planned for 1.21 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.21 branch in the k/website repo. This PR can be just a placeholder at this time and must be created by March 16 EOD PST Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you!

[k8s-triage-robot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[saschagrunert]

Targeting stable for Kubernetes v1.27.

[Atharva-Shinde]

Hello @derekwaynecarr @saschagrunert 👋, Enhancements team here.

Just checking in as we approach Enhancements freeze on 18:00 PDT Thursday 9th February 2023.

This enhancement is targeting for stage stable for 1.27 (correct me, if otherwise)

Here's where this enhancement currently stands:

• [ ] KEP readme using the latest template has been merged into the k/enhancements repo.
• [X] KEP status is marked as implementable for latest-milestone: 1.27
• [ ] KEP readme has a updated detailed test plan section filled out
• [X] KEP readme has up to date graduation criteria
• [ ] KEP has a production readiness review that has been completed and merged into k/enhancements.

For this KEP, we would just need to update the following:

• Add response for this question in the Scalability questionnaire of the KEP readme
• Update this enhancement's test plan section to be in compliance with the current detailed test plan of the KEP readme template

The status of this enhancement is marked as at risk. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

[johnbelamaric]

Can we get the KEP updated and make sure all the stable PRR questions are answered ASAP?

[johnbelamaric]

Oh, I see the PR here: https://github.com/kubernetes/enhancements/pull/3719

In the future please tag the issue so it shows up on here.

[saschagrunert]

Updating the test section in https://github.com/kubernetes/enhancements/pull/3865

Should be mostly a no-op, since it's only a formal change.

[SergeyKanzhelev]

Production readiness completed

https://github.com/kubernetes/enhancements/blob/b3a825e2748be8ef3c5567eb290168ec4ebd5182/keps/prod-readiness/sig-node/2053.yaml#L4-L5

and template updated to the latest including the test plan.

@Atharva-Shinde this KEP should be good to go

[marosset]

This enhancement meets all the requirements to be tracked for v1.27 Thanks @saschagrunert @SergeyKanzhelev

[katmutua]

Hello @saschagrunert and @SergeyKanzhelev 👋🏾 !

@katmutua 1.27 Release Docs shadow here. This enhancement is marked as ‘Needs Docs’ for 1.27 release.

Please follow the steps detailed in the documentation to open a PR against dev-1.27 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by March 16. For more information, please take a look at Documenting for a release to familiarize yourself with the documentation requirements for the release.

If you already have existing open PRs please link them to the description so we can easily track them. Thanks!

[saschagrunert]

Thank you @katmutua, the placeholder PR is now available in https://github.com/kubernetes/website/pull/39905