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
Respect PodTopologySpread after rolling upgrades #3243
Comments
/sig scheduling |
/assign |
/milestone v1.25 |
Hello @denkensk 👋, 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:
For note, the status of this enhancement is marked as |
Hi @denkensk Enhancements team here again 👋 Checking in as we approach Code Freeze at 01:00 UTC on Wednesday, 3rd August 2022. Please ensure that the following items are completed before the code-freeze:
Currently, the status of the enhancement is marked as Thanks :) |
Hey @denkensk as kubernetes/kubernetes#111441 PR is now merged and included in the issue description, I have marked this enhancement as |
@denkensk can you please open a docs PR? |
Sorry. I created it before, forgot to link it with this issue. kubernetes/website#35165 |
Hope to see this feature promoting to beta in v1.27, we delayed our blog about the improvements of PodTopologySpread in recent several releases, and we hope to post one in v1.27, including If you're out of bandwidth, I can help with you @denkensk |
Thanks. I will promote it to beta in v1.27. |
@denkensk note that the Enhancements freeze has been set for February 10th. |
OK Thanks. I am working on this and will submit PR this week. |
/label lead-opted-in |
/stage beta |
Hello @denkensk 👋, v1.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:
For this KEP, we would need to update the following:
#3740 might address this, once it's merged. The status of this enhancement is marked as |
Thank you @denkensk ! This is almost there, there is a new question in the PRR Scalability that you might want to address:
The Scalability section of the PRR is mandatory for |
Done @fsmunoz |
Thank you @denkensk !
This enhancement is ready to be traced for graduation to beta in v1.27. |
Hi @denkensk 👋, 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:
For this enhancement, it looks like all linked PRs are merged. Please let me know what other PRs in k/k I should be tracking for this KEP. As always, we are here to help should questions come up. Thanks! |
Enhancement Description
k/enhancements
) update PR(s): KEP-3243: respect pod topology spread after rolling upgrades #3244k/k
) update PR(s): Respect PodTopologySpread after rolling upgrades kubernetes#111441k/website
) update PR(s): Add docs for MatchLabelKeysInPodTopologySpread feature website#35165k/enhancements
) update PR(s): KEP-3243: Graduate MatchLabelKeys In PodTopologySpread to beta #3740k/k
) update PR(s): feat: graduate matchLabelKeys in podTopologySpread to beta kubernetes#116291k/website
) update(s): doc: graduate matchLabelKeys in podTopologySpread to beta website#39826Please 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: