New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PodHealthyPolicy for PodDisruptionBudget #3017
Comments
/sig apps |
/cc |
/milestone v1.24 |
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 Here’s where this enhancement currently stands:
The status of this enhancement is marked as |
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! |
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 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! |
Hi @mortent We’re reminding people with KEPs that need docs to open a placeholder PR. |
@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. |
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 Thanks! |
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 |
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 |
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-triage-robot: Closing this issue. In response to this:
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. |
adding to 1.27 to target beta promotion. @atiratree, are there any KEP updates needed to prep for beta work? |
@liggitt thanks. The KEP should reflect the reality, so no prep needed. Only an update for the beta graduation itself. |
/stage beta |
opened a KEP update for the Beta promotion #3777 |
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 Here's where this enhancement currently stands:
It looks like #3777 will address most of these issues. The status of this enhancement is marked as |
@npolshakova the KEP update just merged and description should be up-to-date |
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. |
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! |
/unassign mortent |
I have opened the docs update kubernetes/website#40017 |
/milestone clear |
Enhancement Description
Add
PodHealthyPolicy
to PodDisruptionBudgetk/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: