PodHealthyPolicy for PodDisruptionBudget

[mortent]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Add PodHealthyPolicy to PodDisruptionBudget
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-apps/3017-pod-healthy-policy-for-pdb/README.md
• Discussion Link: https://www.youtube.com/watch?v=rP-XUjyCaps&list=PL69nYSiGNLP2LMq7vznITnpd2Fk1YIZF3
• Primary contact (assignee): @ravisantoshgudimetla @atiratree
• Responsible SIGs: sig-apps
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.26
  • Beta release target (x.y): 1.27
  • Stable release target (x.y): 1.31
• Alpha
  • KEP (k/enhancements) update PR(s):
    • KEP-3017: Pod Healthy Policy for PDBs #3018
    • KEP-3017: Update timeframe for the PDB health policy #3546
    • Update KEP-3017: Test Plan section #3584
    • KEP-3017: rewrite PodHealthyPolicy KEP into UnhealthyPodEvictionPolicy #3677
  • Code (k/k) update PR(s):
    • api: add unhealthyPodEvictionPolicy for PDBs kubernetes#113375
  • Docs (k/website) update PR(s):
    • Add documentation for Unhealthy Pod Eviction Policy for PDBs website#37768
• Beta
  • KEP (k/enhancements) update PR(s):
    • KEP-3017: Promote unhealthyPodEvictionPolicy for PDBs to Beta #3777
    • Update beta graduation criteria #3883
  • Code (k/k) update PR(s):
    • Promote pdb healthy to beta kubernetes#115363
    • Update docs for promoting PodHealthyPolicy of PDB to beta kubernetes#115914
    • Add a warning event when pdb has found a unmanaged pod kubernetes#115861
  • Docs (k/website) update(s):
    • Update docs for PodDisruptionBudget unhealthy pod eviction policy promotion to Beta website#40017
• Stable
  • KEP (k/enhancements) update PR(s):
    • KEP-3017: Graduate UnhealthyPodEvictionPolicy for PDBs to stable #4469
    • KEP-3017: Graduate UnhealthyPodEvictionPolicy for PDBs to stable #4669
  • Code:
    • promote PDBUnhealthyPodEvictionPolicy to GA kubernetes#123428
  • Docs:
    • [KEP-3017]: promote PDBUnhealthyPodEvictionPolicy to GA website#45263
    • [WIP] [KEP-3017]: feature blog for UnhealthyPodEvictionPolicy for PDBs to GA website#45269

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

[mortent]

/sig apps

[shivanshuraj1333]

/cc

[soltysh]

/milestone v1.24

[hosseinsalahi]

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:

• Updated KEP file using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for this release
• KEP has a test plan section filled out.
• KEP 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 KEP link and the description up-to-date.
Thanks!

[mehabhalodiya]

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]

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:

• All PRs to the Kubernetes repo that are related to your enhancement are merged by the code freeze deadline.
• Have a documentation placeholder PR open by 18:00 PDT, Thursday, March 31, 2022.

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?

• Add PodHealthyPolicy for PDBs kubernetes#108233

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

[mehabhalodiya]

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]

@mehabhalodiya I have created a placeholder PR for the docs: kubernetes/website#32567

@encodeflush Yes, I can confirm that kubernetes/kubernetes#108233 is the implementation of this feature.

[gracenng]

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]

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.

[salehsedghpour]

Hello @atiratree and @ravisantoshgudimetla 👋 Enhancements team here,

Unfortunately, the implementation (code related) PR(s) associated with this enhancement is not in the merge-ready state by code-freeze and hence this enhancement is now removed from the v1.30 milestone.

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

/milestone clear

[sreeram-venkitesh]

Hi 👋, 1.31 Enhancements Lead here.

If you wish to progress this enhancement in v1.31, please have the SIG lead opt-in your enhancement by adding the lead-opted-in label and set the milestone to v1.31 before the Production Readiness Review Freeze.

/remove-label lead-opted-in

[atiratree]

I plan to graduate this feature to GA in 1.31:

KEP update: #4669

[soltysh]

/label lead-opted-in
/milestone v1.31

[sreeram-venkitesh]

Hello @atiratree 👋, v1.31 Enhancements team here.

Just checking in as we approach enhancements freeze on 02:00 UTC Friday 14th June 2024 / 19:00 PDT Thursday 13th June 2024.

This enhancement is targeting for stage stable for v1.31 (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: v1.31. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria
• 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 (6th June) so that the PRR team has enough time to review your KEP before the enhancements freeze.

For this KEP, #4669 takes care of all the changes required. Please make sure that it is merged in time before the enhancements freeze!

The status of this enhancement is marked as At risk for enhancements freeze. Once the above PR is merged, I can mark it as tracked.

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

[sreeram-venkitesh]

With #4669 merged, we can mark this KEP as tracked for enhancements freeze 🎉

[salaxander]

Hello @atiratree 👋, 1.31 Docs Shadow here.

Does the work related to this KEP planned for 1.31 require any new docs or modification to existing docs?

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

Also, take a look at Documenting for a release to get yourself familiarised with the docs requirement for the release.

Thank you!

[edithturn]

Hello, @atiratree and @ravisantoshgudimetla!

👋 from the v1.31 Communications Team!

We'd love for you to opt in to write 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 3rd July, 2024. For more information about writing a blog see the blog contribution guidelines.

Note: In your placeholder PR, use XX characters for the blog date in the front matter and file name. We will work with you on updating the PR with the publication date once we have a final number of feature blogs for this release.

[atiratree]

@salaxander opened a placeholder PR for the docs kubernetes/website#45263

[sreeram-venkitesh]

Hey again @atiratree 👋 v1.31 Enhancements team here,

Just checking in as we approach code freeze at 02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 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.

List of associated PRs:

• promote PDBUnhealthyPodEvictionPolicy to GA kubernetes#123428

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

This KEP is marked as Tracked for code freeze. Thanks a lot for keeping the issue description up to date! 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!

[tjons]

Closing this as it was implemented in the 1.31 release. Thanks all!