search

kubernetes / enhancements

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

PodHealthyPolicy for PodDisruptionBudget #3017

Closed mortent closed 1 month ago

mortent commented 2 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.

mortent commented 2 years ago

/sig apps

shivanshuraj1333 commented 2 years ago

/cc

soltysh commented 2 years ago

/milestone v1.24

hosseinsalahi commented 2 years ago

Hello @mortent

v1.24 Enhancements team here.

Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd, 2022. This enhancement is targeting alpha for v1.24,

Here’s where this enhancement currently stands:

The status of this enhancement is marked as tracked. Please keep the issue KEP link and the description up-to-date.
Thanks!

mehabhalodiya commented 2 years ago

Hi @mortent 👋🏻 1.24 Docs shadow here.

This enhancement is marked as 'Needs Docs' for the 1.24 release.

Please follow the steps detailed in the documentation to open a PR against the dev-1.24 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thu March 31, 11:59 PM PDT.

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

Thanks!

hosseinsalahi commented 2 years ago

Hello @mortent

I'm just checking in once more as we approach the 1.24 Code Freeze on 18:00 PDT, Tuesday, March 29th 2022

Please ensure the following items are completed:

For note, the status of this enhancement is currently marked as at risk.

Could you please confirm if following PR is part of the implementation for this enhancement?

Kindly please let me know if I'm missing any related PRs other than the ones I linked above. Thank you so much!

mehabhalodiya commented 2 years ago

Hi @mortent We’re reminding people with KEPs that need docs to open a placeholder PR. Although the deadline for this is March 31, we have more than 30 that have yet to be opened, so we’re trying to get ahead of it. Let me know if you have any questions. Thanks!

mortent commented 2 years ago

@mehabhalodiya I have created a placeholder PR for the docs: https://github.com/kubernetes/website/pull/32567

@encodeflush Yes, I can confirm that https://github.com/kubernetes/kubernetes/pull/108233 is the implementation of this feature.

gracenng commented 2 years ago

Hi, 1.24 Enhancements Lead here 👋. With code freeze now in effect, this enhancement has not met the criteria for the freeze and has been removed from the milestone.

As a reminder, the criteria for code freeze is:

All PRs to the kubernetes/kubernetes repo have merged by the code freeze deadline Feel free to file an exception to add this back to the release. If you plan to do so, please file this as early as possible.

Thanks! /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/3017#issuecomment-1229108227): >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.
soltysh commented 2 years ago

/milestone v1.26 /label lead-opted-in /remove-lifecycle rotten

soltysh commented 2 years ago

/stage alpha

rhockenbury commented 2 years ago

/label tracked/yes /remove-label tracked/no

Atharva-Shinde commented 2 years ago

Hey @mortent 👋, 1.26 Enhancements team here!

Just checking in as we approach Enhancements Freeze on 18:00 PDT on Thursday 6th October 2022.

This enhancement is targeting for stage alpha for 1.26

Here's where this enhancement currently stands:

For this KEP, we would need to:

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 :)

atiratree commented 2 years ago

The KEP needs updating it's Test Plan Section to incorporate details as stated in the updated detailed test plan

opened a PR for the test plan update: https://github.com/kubernetes/enhancements/pull/3584

Update the kep.yaml to reflect the current milestone information

the milestone information should be correct in the kep.yaml already: https://github.com/kubernetes/enhancements/pull/3546

soltysh commented 2 years ago

@Atharva-Shinde with #3584 in this should all be good.

Atharva-Shinde commented 2 years ago

Hey @atiratree @soltysh @mortent, as #3584 is merged with required changes, I've updated the status of this KEP to tracked for v1.26 release cycle :)

Atharva-Shinde commented 1 year ago

Hey @mortent @atiratree 👋,

Checking in as we approach 1.26 code freeze at 17:00 PDT on Tuesday 8th November 2022.

Please ensure the following items are completed:

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

cathchu commented 1 year ago

Hello @mortent and @atiratree 👋 1.26 Release Docs shadow here!

This enhancement is marked as ‘Needs Docs’ for 1.26 release. Please follow the steps detailed in the documentation to open a PR against dev-1.26 branch in the k/website repo. This PR can be just a placeholder at this time, and must be created by November 9. Also, take a look at Documenting for a release to familiarize yourself with the docs requirement for the release.

Thank you!

Atharva-Shinde commented 1 year ago

Hey @mortent @atiratree 👋, just a quick check-in again before 1.26 code freeze at 17:00 PDT Tuesday 8th November 2022 i.e tomorrow. Looks like we would at least need to get the code PR/s: https://github.com/kubernetes/kubernetes/pull/113375 and https://github.com/kubernetes/kubernetes/pull/113376 (any more PRs?) merged before the code-freeze. Could you also please update the Issue Description with related PRs:)

atiratree commented 1 year ago

@cathchu thanks, I have opened a placeholder PR https://github.com/kubernetes/website/pull/37768

@mortent: could you please update the description?

@Atharva-Shinde: yes it is only these two PRs. I have also created an exception request for a 5 day extension.

rhockenbury commented 1 year ago

Hello 👋, 1.26 Enhancements Lead here.

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

If you still wish to progress this enhancement in v1.26, please file an exception request. Thanks!

/milestone clear /label tracked/no /remove-label tracked/yes /remove-label lead-opted-in

soltysh commented 1 year ago

@rhockenbury based on the exception granted I think we should bring this back to 1.26 milestone

leonardpahlke commented 1 year ago

/milestone v1.26 /label tracked/yes /label lead-opted-in /remove-label tracked/no

cathchu commented 1 year ago

Hey @atiratree, 1.26 Docs Shadow here 👋 !

Just a gentle reminder that the deadline (November 15th) for PRs ready to review has passed.

Please complete https://github.com/kubernetes/website/pull/37768 and request a review as soon as possible.

Thanks you!

CC @krol3

krol3 commented 1 year ago

Hi @atiratree here Doc Lead 1.26, I need help with this PR, the deadline has passed.

atiratree commented 1 year ago

I have created PRs for the blog update https://github.com/kubernetes/website/pull/37627 and the KEP update https://github.com/kubernetes/enhancements/pull/3677

marosset commented 1 year ago

/remove-label lead-opted-in /remove-label tracked/yes /label tracked/no /milestone clear

liggitt commented 1 year ago

adding to 1.27 to target beta promotion. @atiratree, are there any KEP updates needed to prep for beta work?

atiratree commented 1 year ago

@liggitt thanks. The KEP should reflect the reality, so no prep needed. Only an update for the beta graduation itself.

soltysh commented 1 year ago

/stage beta /label lead-opted-in

atiratree commented 1 year ago

opened a KEP update for the Beta promotion https://github.com/kubernetes/enhancements/pull/3777

npolshakova commented 1 year ago

Hello @atiratree 👋, 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 beta for 1.27 (correct me, if otherwise)

Here's where this enhancement currently stands:

It looks like https://github.com/kubernetes/enhancements/pull/3777 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!

atiratree commented 1 year ago

@npolshakova the KEP update just merged and description should be up-to-date

npolshakova commented 1 year ago

Hi @atiratree,

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:

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!

LukeMwila commented 1 year ago

Hi @mortent, 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!

soltysh commented 1 year ago

/unassign mortent /assign @ravisantoshgudimetla @atiratree

atiratree commented 1 year ago

I have opened the docs update https://github.com/kubernetes/website/pull/40017

Atharva-Shinde commented 1 year ago

/milestone clear

atiratree commented 9 months ago

I will try to graduate this feature to GA in 1.30

soltysh commented 8 months ago

/stage stable /label lead-opted-in

atiratree commented 8 months ago

I have opened the PR for graduation: https://github.com/kubernetes/enhancements/pull/4469

soltysh commented 8 months ago

/milestone v1.30

pnbrown commented 8 months ago

Hello @atiratree 👋, Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 9th February 2024.

This enhancement is targeting for stage stable for v1.30 (correct me, if otherwise)

Here’s where this enhancement currently stands:

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀

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

celestehorgan commented 8 months ago

👋 Reminder to open a PR to Update the feature gate and flags to stable for this release!

If there's additional changes from the beta to stable versions, please open a placeholder instead!

natalisucks commented 8 months ago

Hi @atiratree and @ravisantoshgudimetla,

👋 from the v1.30 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement!

We encourage blogs for features including, but not limited to: breaking changes, features and changes important to our users, and features that have been in progress for a long time and are graduating.

To opt in, you need to open a Feature Blog placeholder PR against the website repository. The placeholder PR deadline is 27th February, 2024.

Here's the 1.30 Release Calendar

atiratree commented 7 months ago

hi, I have opened placeholder PRs: