graduate the kubelet podresources endpoint to GA

[ffromani]

Enhancement Description

• One-line enhancement description (can be used as a release note): promote to GA the kubelet podresources API endpoint
• Kubernetes Enhancement Proposal: TODO
• Discussion Link:
  • SIG Node - 1.27 Planning discussed on SIG Node weekly on [13th December 2022]
  • SIG Node - 1.28 Planning discussed on SIG Node weekly on [2nd May 2023]
• Primary contact (assignee): @ffromani
• Responsible SIGs: sig-node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.13
  • Beta release target (x.y): 1.15
  • Stable release target (x.y): 1.28
• Stable
  • KEP (k/enhancements) update PR(s):
    • KEP-606: finalize podresources API GA graduation #3791
    • KEP-606: clarify GA blockers #3863
    • node: podresources: GA in 1.28 #3980
  • Code (k/k) update PR(s):
    • node: create podresources endpoint also on windows kubernetes#115133
    • add podresources DOS prevention using rate limit kubernetes#116459
    • e2e: node remove: kubevirt device plugin kubernetes#115926
    • node: podresources: graduate to GA kubernetes#116525
  • Docs (k/website) update(s):
    • WIP: node: graduate the podresources API endpoint to GA website#39959
    • node: graduate the podresources API endpoint to GA website#41506
    • node: fix release state for podresources API website#41804

I don't own the original issue (#606) which is also CLOSED, so filed this new one

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[ffromani]

/sig node

[SergeyKanzhelev]

/milestone v1.27

[SergeyKanzhelev]

/assign @ffromani

[SergeyKanzhelev]

/label lead-opted-in

[SergeyKanzhelev]

/stage stable

[npolshakova]

Hello @ffromani 👋, 1.27 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.
• KEP status is marked as implementable for latest-milestone: 1.27
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

It looks like #3791 will address most of these issues.

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!

[SergeyKanzhelev]

Status implementable:

enhancements/keps/sig-node/606-compute-device-assignment/kep.yaml

Line 9 in 472a381

status: implementable

milestones are correct:

enhancements/keps/sig-node/606-compute-device-assignment/kep.yaml

Lines 21 to 33 in 472a381

	# The target maturity stage in the current dev cycle for this KEP.
	stage: stable
	# The most recent milestone for which work toward delivery of this KEP has been
	# done. This can be the current (upcoming) milestone, if it is being actively
	# worked on.
	latest-milestone: "v1.27"
	# The milestone at which this feature was, or is targeted to be, at each stage.
	milestone:
	alpha: "v1.13"
	beta: "v1.15"
	stable: "v1.27"

Test plan complete: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/606-compute-device-assignment/README.md#test-plan

@npolshakova This KEP should be good to go

[npolshakova]

Great! Looks like #3791 has gone in so this is now tracked for 1.27 🚀

[npolshakova]

Hi @ffroman,

Checking in as we approach 1.27 code freeze at 17:00 PDT on Tuesday 14th March 2023.

Please ensure the following items are completed:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.
  • e2e: node remove: kubevirt device plugin kubernetes#115926

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze:

• node: create podresources endpoint also on windows kubernetes#115133
• node: podresources: add rate limiting kubernetes#115852

Please let me know if there are any other PRs in k/k I should be tracking for this KEP.
As always, we are here to help should questions come up. Thanks!

[ffromani]

Hi @npolshakova , thanks for the reminder. Your assessment is accurate as things are today (March 9). I'll make sure the progress on this work is tracked accurately as the code freeze date approaches.

[taniaduggal]

Hi @ffromani 👋 , I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 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.
Please feel free to reach out with any questions. Thanks!

[ffromani]

Hi @ffromani wave , I’m reaching out from the 1.27 Release Docs team. This enhancement is marked as ‘Needs Docs’ for the 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. Please feel free to reach out with any questions. Thanks!

thanks! Here: kubernetes/website#39959 (indeed very much WIP)

[npolshakova]

Hi @ffroman, this is the status as we approach code freeze today:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PRs are fully merged by the code freeze deadline.

For this enhancement, it looks like the following PRs need to merge:

• node: create podresources endpoint also on windows kubernetes#115133
• add podresources DOS prevention using rate limit kubernetes#116459
• e2e: node remove: kubevirt device plugin kubernetes#115926
• node: podresources: graduate to GA kubernetes#116525

Please let me know what other PRs in k/k I should be tracking for this KEP.

As always, we are here to help should questions come up. Thanks!

[ffromani]

hi @npolshakova your assessment is correct. Thanks.

[npolshakova]

Unfortunately the implementation PRs associated with this enhancement have not merged by code-freeze so this enhancement is getting removed from the release.

It looks like kubernetes/kubernetes#116525 had the lgtm label removed as part of the rebase.

If you would like to file an exception please see https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md

/milestone clear
/remove-label tracked/yes
/label tracked/no

[SergeyKanzhelev]

/reopen

[k8s-ci-robot]

@SergeyKanzhelev: Reopened this issue.

In response to this:

/reopen

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.

[SergeyKanzhelev]

for docs update

[SergeyKanzhelev]

/label lead-opted-in

[npolshakova]

Hi @ffromani 👋, 1.28 Enhancements team here!

Just checking in as we approach enhancements freeze on 01:00 UTC Friday, 16th June 2023.

This enhancement is targeting for stage stable for 1.28 (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.
• KEP status is marked as implementable for latest-milestone: 1.28
• KEP readme has a updated detailed test plan section filled out
• KEP readme has up to date graduation criteria
• KEP has a production readiness review that has been completed and merged into k/enhancements.

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

[npolshakova]

Hey again @ffromani 👋

Just checking in as we approach Code freeze at 01:00 UTC Friday, 19th July 2023 .

Here’s the enhancement’s state for the upcoming code freeze:

• All the PRs that are related to your enhancement are linked in the above issue description (for tracking purposes). This includes code, tests, and documentation related PR/s.
• All code related PR/s are merged or are in merge-ready state ( i.e they have approved and lgtm labels applied) by the code freeze deadline. This includes any tests related PR/s too.
  • node: create podresources endpoint also on windows kubernetes#115133
  • add podresources DOS prevention using rate limit kubernetes#116459
  • e2e: node remove: kubevirt device plugin kubernetes#115926
  • node: podresources: graduate to GA kubernetes#116525

Also please let me know if there are other PRs in k/k we should be tracking for this KEP.
As always, we are here to help if any questions come up. Thanks!

[Atharva-Shinde]

Hey @ffromani 👋 Enhancements Lead here,
With all implementation PRs merged as per the issue description, this enhancement is now tracked for v1.28 Code Freeze!
kubernetes/kubernetes#115133
kubernetes/kubernetes#116459
kubernetes/kubernetes#115926
kubernetes/kubernetes#116525

[npolshakova]

/remove-label lead-opted-in

[ffromani]

all PRs merged, work completed in 1.28.0; now we have 1.28.1 out, so we can close.