search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.41k stars 1.47k forks source link

Pod level resources #2837

Open n4j opened 3 years ago

n4j commented 3 years ago

Enhancement Description

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

n4j commented 3 years ago

/sig node

n4j commented 3 years ago

/sig cli architecture cloud-provider

n4j commented 3 years ago

/assign @derekwaynecarr @thockin

k8s-triage-robot commented 2 years ago

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:

You can:

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

/lifecycle stale

n4j commented 2 years ago

/remove-lifecycle stale

rhockenbury commented 2 years ago

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:

The status of this enhancement is at risk. Thanks!

gracenng commented 2 years ago

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 commented 2 years ago

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:

You can:

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

/lifecycle stale

k8s-triage-robot commented 2 years ago

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:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 2 years ago

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:

You can:

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

/close

k8s-ci-robot commented 2 years ago

@k8s-triage-robot: Closing this issue.

In response to [this](https://github.com/kubernetes/enhancements/issues/2837#issuecomment-1173308464): >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][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
n4j commented 2 years ago

/reopen

k8s-ci-robot commented 2 years ago

@n4j: Reopened this issue.

In response to [this](https://github.com/kubernetes/enhancements/issues/2837#issuecomment-1242624028): >/reopen Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
SergeyKanzhelev commented 2 years ago

/remove-lifecycle rotten

Since this is being looked at...

KnVerey commented 1 year ago

/remove-label sig/cli

k8s-ci-robot commented 1 year ago

@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](https://github.com/kubernetes/enhancements/issues/2837#issuecomment-1281094309): >/remove-label sig/cli Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
k8s-triage-robot commented 1 year ago

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:

You can:

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

/lifecycle stale

n4j commented 1 year ago

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

k8s-ci-robot commented 1 year ago

@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](https://github.com/kubernetes/enhancements/issues/2837#issuecomment-1450641749): >/remove-label help-wanted > Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
thockin commented 1 year ago

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

n4j commented 1 year ago

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

Sure @thockin

n4j commented 1 year ago

/remove-help

SergeyKanzhelev commented 1 year ago

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

n4j commented 1 year ago

@SergeyKanzhelev yes 🙂.

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

n4j commented 1 year ago

@thockin Gentle bump 🙂

SergeyKanzhelev commented 1 year ago

@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

salehsedghpour commented 8 months ago

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

k8s-triage-robot commented 5 months ago

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

This bot triages un-triaged issues according to the following rules:

You can:

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

/lifecycle stale

n4j commented 5 months ago

/remove-lifecycle stale

SergeyKanzhelev commented 4 months ago

/milestone v1.31

ndixita commented 4 months ago

@n4j could you please update the KEP link and release targets in the issue description. https://github.com/kubernetes/enhancements/pull/4678 targeting alpha in 1.31

SergeyKanzhelev commented 4 months ago

/assign @ndixita

SergeyKanzhelev commented 4 months ago

/stage alpha

mrunalp commented 4 months ago

/label lead-opted-in

mickeyboxell commented 4 months ago

Hi @n4j 👋 v1.31 Enhancements team here.

I wanted to check in as we approach the enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

This enhancement is targeting alpha for v1.31. Please correct me if that isn't the case.

Here's where this enhancement currently stands:

For this KEP, we need to do the following:

The status of this enhancement is marked as at risk for enhancement freeze. We can mark it as tracked as soon as the above changes are merged. Please make sure to get this done before the enhancements freeze.

If you anticipate missing enhancements freeze, you can file an exception request in advance. Let me know if you have any questions! Thank you!

mickeyboxell commented 4 months ago

Hi @n4j @ndixita I wanted to follow up prior to the enhancements freeze tomorrow. Do you think you'll have some time today or tomorrow to address the comments above?

ndixita commented 4 months ago

Hi @n4j @ndixita I wanted to follow up prior to the enhancements freeze tomorrow. Do you think you'll have some time today or tomorrow to address the comments above?

yes, I am trying to address some of the comments later today.

mickeyboxell commented 3 months ago

Hi @ndixita 👋, v1.31 Enhancements team here.

Unfortunately, this enhancement did not meet requirements for enhancements freeze.

If you still wish to progress this enhancement in v1.31, please file an exception request as soon as possible, within three days. If you have any questions, you can reach out in the #release-enhancements channel on Slack and we'll be happy to help. Thanks!

sreeram-venkitesh commented 3 months ago

/milestone clear

sreeram-venkitesh commented 3 months ago

/label tracked/no

tjons commented 3 weeks ago

Hi, enhancements lead here - I inadvertently added this to the 1.32 tracking board 😀. Please readd it if you wish to progress this enhancement in 1.32.

/remove-label lead-opted-in

ndixita commented 3 weeks ago

@tjons I would like to get this added to 1.32. Could you please help me get this KEP added?

tjons commented 3 weeks ago

done! /label lead-opted-in /milestone v1.32

tjons commented 3 weeks ago

/label lead-opted-in

sftim commented 2 weeks ago

Hi! I'm from SIG Docs.

This sounds like a really popular enhancement. If it's likely to land in a release, please check in with SIG Release and SIG Docs about how we'll revise the documentation. #release-docs (on Kubernetes Slack) for work planning, or #sig-docs to liaise around good practice for technical writing.

impact-maker commented 1 week ago

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

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

This enhancement is targeting for stage alpha for v1.32 (correct me, if otherwise).

Here's where this enhancement currently stands:

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

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

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

ndixita commented 1 week ago

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

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024.

This enhancement is targeting for stage alpha for v1.32 (correct me, if otherwise).

Here's where this enhancement currently stands:

  • [x] KEP readme using the latest template has been merged into the k/enhancements repo.
  • [ ] KEP status is marked as implementable for latest-milestone: v1.32.
  • [x] KEP readme has up-to-date graduation criteria.
  • [x] KEP has submitted a production readiness review request for approval and has a reviewer assigned.
  • [ ] KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 3rd October 2024 so that the PRR team has enough time to review your KEP.

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

  • [ ] KEP status is marked as implementable for latest-milestone: v1.32.
  • [ ] KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline on Thursday 3rd October 2024 so that the PRR team has enough time to review your KEP.

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

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

I have marked the KEP as implementable for 1.32 and have filled the PRR questionnaire.

haircommander commented 1 day ago

Since PRR and a node review has the baseline PR merged, I am moving this to tracked from the SIG node board's perspective. there's one follow-up in https://github.com/kubernetes/enhancements/pull/4915 but by and large this looks good for enhancement freeze from my perspective

dipesh-rawat commented 3 hours ago

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

Now that PR https://github.com/kubernetes/enhancements/pull/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!