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
Min domains in PodTopologySpread #3022
Comments
/sig scheduling |
/cc @x13n |
update the description to link to the merged KEP, instead of linking to the PR that added it. |
/milestone v1.24 |
Hello @sanposhiho 👋, 1.24 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00pm PT on Thursday Feb 3rd, 2022. For note, This enhancement is targeting for stage Here’s where this enhancement currently stands:
With all the KEP requirements in place & merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. 🚀 For note, the status of this enhancement is marked as |
Hi @alculquicondor 👋 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 Thursday 31st March 2022, 18:00 PDT. Also, if needed take a look at Documenting for a release to familiarize yourself with the docs requirement for the release. Thanks! |
Hello @alculquicondor 👋 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 Kindly please let me know if I'm missing any open PRs other than the ones I linked above. Thank you so much! |
@sanposhiho can you work on the documentation as well? |
Sure, I will update doc and kep this weekend. |
There is no need to update the KEP. |
@sanposhiho I see already opened up PR: kubernetes/website/pull/32340 |
Hm, looks like other person updated the doc instead of me. Thanks for informing @mehabhalodiya. |
Will you please update the issue description? |
@alculquicondor |
@sanposhiho @alculquicondor, thank you so much. With the Docs PR kubernetes/website#32340 open now, all requirements for Code Freeze are finished. The status is now |
added to the tracking sheet too |
Thanks |
Hello @sanposhiho 👋, 1.25 Enhancements team here. Just checking in as we approach enhancements freeze on 18:00 PST on Thursday June 23, 2022. For note, This enhancement is targeting for stage Here's where this enhancement currently stands:
Looks like for this one, we would need to update the open KEP PR #3338 & get it merged by the Enhancements Freeze:
For note, the status of this enhancement is marked as |
Hello @sanposhiho. Just checking in, as we are four days away from the enhancements freeze on Thursday, June 23, 2022 at 18:00 PM PT. Kindly ensure PR #3338 is merged before then. Please note: the current status of the enhancement is |
@jasonbraganza We merged #3338 👍 |
Thanks so much @sanposhiho. With KEP PR #3338 merged, the enhancement is ready for the 1.25 Enhancements Freeze. For note, the status is now marked as |
Can you update the description with the PRs for beta? |
sure, updated |
Hi @sanposhiho 👋 Checking in once more as we approach 1.25 code freeze at 01:00 UTC on Wednesday, 3rd August 2022. Please ensure the following items are completed:
Please verify, if there are any additional k/k PRs besides the ones listed above. |
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 |
/remove-lifecycle stale |
@sanposhiho can you graduate to GA in 1.27? The enhancements freeze is set to February 10th. |
@alculquicondor |
Oh, we should wait until 1.29 then. |
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 |
/remove-lifecycle stale |
Enhancement Description
k/enhancements
) update PR(s):k/k
) update PR(s):k/website
) update PR(s):k/enhancements
) update PR(s): [KEP-3022] Write the production readiness requirements to graduate to beta #3338k/k
) update PR(s): Graduate MinDomains in Pod Topology Spread to beta kubernetes#110388k/website
) update(s): Update the doc for minDomains to graduate minDomains to beta website#35202Please 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: