enhancements icon indicating copy to clipboard operation
enhancements copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes

Pod level resource limits

Open n4j opened this issue 2 years ago • 29 comments

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/pull/1592
  • Discussion Link: https://www.youtube.com/watch?v=3cU56ZiUZ8w&list=PL69nYSiGNLP1wJPj5DYWXjiArF-MJ5fNG&index=100&ab_channel=DerekCarr
  • Primary contact (assignee): @n4j
  • Responsible SIGs: sig/node
  • Enhancement target (which target equals to which milestone):
    • Alpha release target (x.y): 1.23
    • Beta release target (x.y): 1.23
    • Stable release target (x.y): 1.23
  • [ ] Alpha
    • [x] KEP (k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/1592
    • [ ] Code (k/k) update PR(s):
    • [ ] Docs (k/website) update PR(s):

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

n4j avatar Jul 27 '21 03:07 n4j

/sig node

n4j avatar Jul 27 '21 03:07 n4j

/sig cli architecture cloud-provider

n4j avatar Jul 27 '21 03:07 n4j

/assign @derekwaynecarr @thockin

n4j avatar Jul 27 '21 03:07 n4j

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 avatar Nov 01 '21 14:11 k8s-triage-robot

/remove-lifecycle stale

n4j avatar Nov 09 '21 03:11 n4j

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 #1592
  • [ ] KEP status is marked as implementable for latest-milestone: 1.24 - INCOMPLETE IN PR #1592
  • [ ] KEP has a test plan section filled out. - INCOMPLETE IN PR #1592
  • [ ] KEP has up to date graduation criteria. - INCOMPLETE IN PR #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!

rhockenbury avatar Jan 20 '22 20:01 rhockenbury

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

/milestone clear

gracenng avatar Feb 04 '22 02:02 gracenng

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 avatar May 05 '22 03:05 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 avatar Jun 04 '22 03:06 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-triage-robot avatar Jul 04 '22 03:07 k8s-triage-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.

k8s-ci-robot avatar Jul 04 '22 03:07 k8s-ci-robot

/reopen

n4j avatar Sep 10 '22 04:09 n4j

@n4j: 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.

k8s-ci-robot avatar Sep 10 '22 04:09 k8s-ci-robot

/remove-lifecycle rotten

Since this is being looked at...

SergeyKanzhelev avatar Sep 26 '22 22:09 SergeyKanzhelev

/remove-label sig/cli

KnVerey avatar Oct 17 '22 15:10 KnVerey

@KnVerey: The label(s) /remove-label sig/cli cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, lead-opted-in, tracked/no, tracked/out-of-tree, tracked/yes. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/remove-label sig/cli

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.

k8s-ci-robot avatar Oct 17 '22 15:10 k8s-ci-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 avatar Jan 15 '23 16:01 k8s-triage-robot

@thockin Sorry for the delay from me on this KEP, I want to restart the discussion on this KEP and bring it to closure

n4j avatar Mar 01 '23 18:03 n4j

@n4j: The label(s) /remove-label help-wanted cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor, lead-opted-in, tracked/no, tracked/out-of-tree, tracked/yes. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to this:

/remove-label help-wanted

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.

k8s-ci-robot avatar Mar 01 '23 18:03 k8s-ci-robot

I'm happy to discuss - but maybe after upstream codefreeze? :)

thockin avatar Mar 01 '23 19:03 thockin

I'm happy to discuss - but maybe after upstream codefreeze? :)

Sure @thockin

n4j avatar Mar 02 '23 02:03 n4j

/remove-help

n4j avatar Mar 02 '23 03:03 n4j

@n4j do you plan to work on this in 1.28 release?

SergeyKanzhelev avatar May 05 '23 22:05 SergeyKanzhelev

@SergeyKanzhelev yes 🙂.

@thockin Can you have a look and approve it provisionally?

n4j avatar May 06 '23 09:05 n4j

@thockin Gentle bump 🙂

n4j avatar May 15 '23 22:05 n4j

@n4j putting this into the milestone to keep track of it. Please update PR - kep.yaml still refers to 1.27 for an alpha.

Since we haven't discussed it in a while - it may be great to come to SIG Node meeting again to find reviewers and approvers for the KEP

/milestone v1.28

SergeyKanzhelev avatar May 26 '23 21:05 SergeyKanzhelev

Hello 👋 1.30 Enhancements Lead here,

I'm closing milestone 1.28 now, If you wish to progress this enhancement in v1.30, please follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board and finally add /milestone v1.30. Thanks!

/milestone clear

salehsedghpour avatar Jan 16 '24 23:01 salehsedghpour

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Apr 16 '24 00:04 k8s-triage-robot

/remove-lifecycle stale

n4j avatar Apr 29 '24 15:04 n4j