Pod level resources

[n4j]

Enhancement Description

• One-line enhancement description (can be used as a release note): Allow setting of resource requests & limits at Pod level
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-node/2837-pod-level-resource-spec/README.md
• Discussion Link: https://www.youtube.com/watch?v=3cU56ZiUZ8w&list=PL69nYSiGNLP1wJPj5DYWXjiArF-MJ5fNG&index=100&ab_channel=DerekCarr
• Primary contact (assignee): @ndixita
• Responsible SIGs: sig/node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.32
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-2837: Pod level resource limits #1592
    • KEP-2837: Introducing Pod level resource specifications with criteria for alpha phase #4678
    • Adding more details to KEP for Pod Level Resources #4915
  • Code (k/k) update PR(s):
    • [PodLevelResources] Pod Level Resources Feature Alpha kubernetes#128407
  • Docs (k/website) update PR(s):
    • [WIP] KEP 2837 (Pod Level Resources) alpha blog website#48475
    • Document pod level resources website#48471

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

[n4j]

/sig node

[n4j]

/sig cli architecture cloud-provider

[n4j]

/assign @derekwaynecarr @thockin

[k8s-triage-robot]

The Kubernetes project currently lacks enough 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 stale
• Mark this issue or PR as rotten with /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 stale

[n4j]

/remove-lifecycle stale

[rhockenbury]

Hi @n4j! 1.24 Enhancements team here. Just checking in as we approach enhancements freeze at 18:00pm PT on Thursday Feb 3rd. I believe this enhancement is targeting alpha for 1.24 - is that correct?

Here’s where this enhancement currently stands:

• Updated KEP file using the latest template has been merged into the k/enhancements repo. - INCLUDED IN PR KEP-2837: Pod level resource limits #1592
• KEP status is marked as implementable for latest-milestone: 1.24 - INCOMPLETE IN PR KEP-2837: Pod level resource limits #1592
• KEP has a test plan section filled out. - INCOMPLETE IN PR KEP-2837: Pod level resource limits #1592
• KEP has up to date graduation criteria. - INCOMPLETE IN PR KEP-2837: Pod level resource limits #1592
• KEP has a production readiness review that has been completed and merged into k/enhancements. - SEE PRR

The status of this enhancement is at risk. Thanks!

[gracenng]

The Enhancements Freeze is now in effect and this enhancement is removed from the release.
Please feel free to file an exception.

/milestone clear

[k8s-triage-robot]

The Kubernetes project currently lacks enough 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 stale
• Mark this issue or PR as rotten with /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 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.

[dipesh-rawat]

Hello @ndixita 👋, v1.32 Enhancements team here,

Now that PR #4678 has been merged, all the KEP requirements are in place and merged into k/enhancements.

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

[spurin]

Hi @ndixita 👋, I'm James Spurin, a 1.32 Docs Shadow. Great to meet you.

Does this enhancement work planned for 1.32 require any new docs or modifications to the existing docs?

If so, please follows the steps here to open a PR against dev-1.32 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday October 24th 2024 18:00 PDT.

Also, take a look at Documenting for a release to familiarise with the docs requirement for the release.

Thank you!

[rashansmith]

Hello @ndixita 👋 from the v1.32 Communications Team!
We'd love for you to consider writing a feature blog about your enhancement! Some reasons why you might want to write a blog for this feature include (but are not limited to) if this introduces breaking changes, is important to our users, or has been in progress for a long time and is graduating.

To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024. For more information about writing a blog see the blog contribution guidelines.

[spurin]

Hi @ndixita 👋,

Just a reminder to open a placeholder PR against dev-1.32 branch in the k/website repo for this (steps available here) for this KEP if it requires new or modifications to existing docs.

The deadline for this is Thursday Oct 24 at 18:00 PDT.

Thanks

James Spurin

[ndixita]

Added the placeholder PRs
kubernetes/website#48475
kubernetes/website#48471

[rashansmith]

Hello @ndixita !

This is a reminder to author your placeholder feature blog post!

To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024. For more information about writing a blog see the blog contribution guidelines.

Please feel free to reach out if you have any questions!

[sftim]

(writing a blog article is optional)

[tjons]

Hey again @ndixita 👋 v1.32 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024 .

Here's where this enhancement currently stands:

• All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
• All PR/s are ready to be merged (they have approved and lgtm labels applied) by the code freeze deadline. This includes tests.

For this enhancement, it looks like the following PRs are open and need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP):

• [PodLevelResources] Pod Level Resources Feature Alpha kubernetes#128407

Additionally, please let me know if there are any other PRs in k/k not listed in the description or not linked with this GitHub issue that we should track for this KEP, so that we can maintain accurate status.

The status of this enhancement is marked as at risk for code freeze.

If you anticipate missing code freeze, you can file an exception request in advance. Thank you!

[ndixita]

@SergeyKanzhelev @haircommander could you please help me attach kubernetes/kubernetes#128407 with the issue.

Also, I am trying my best to get this merged before the deadline, but there could be delays. Will the PR be accepted for exception (in case of delays) as it involves API change?

[haircommander]

done!

[tjons]

Hello @ndixita 👋, Enhancements team here.

With all the implementation(code related) PRs merged as per the issue description:

• [PodLevelResources] Pod Level Resources Feature Alpha kubernetes#128407

This enhancement is now marked as tracked for code freeze for the 1.32 Code Freeze!

Please note that KEPs targeting stable need to have the status field marked as implemented in the kep.yaml file after code PRs are merged and the feature gates are removed.

[fsmunoz]

For completeness sake: the v1.32 Release Team considers this Exception Request CANCELLED: no further action appear to be needed since everything got merged before the Code Freeze being in effect.

[haircommander]

/reopen

A github workflow autoclosed when I set to done 🙃 sorry for the noise

[k8s-ci-robot]

@haircommander: Reopened this issue.

In response to this:

/reopen

A github workflow autoclosed when I set to done 🙃 sorry for the noise

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-sigs/prow repository.