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
Introduce MatchLabelKeys
to Pod Affinity and Pod Anti Affinity
#3633
Comments
@kubernetes/sig-scheduling-leads Do you think we can work on it this release? Or should postpone until the next release? |
I took a review and I think we can include it in 1.27. /label lead-opted-in |
@Huang-Wei Thanks! I'll take a look and modify KEP this weekend. |
/milestone v1.27 |
@sanposhiho: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your Milestone Maintainers Team and have them propose you as an additional delegate for this responsibility. 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. |
/milestone v1.27 |
/stage alpha |
Hello @sanposhiho 👋, 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, it looks like once #3651 merges all the above requirements will be met. The status of this enhancement is marked as |
Hi @sanposhiho - With #3651 merged this enhancement is now Thanks! /label tracked/yes |
Hi @sanposhiho 👋, 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 the following PRs are open and need to be merged before code freeze: 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! |
Unfortunately the implementation PRs associated with this enhancement have not merged by code-freeze so this enhancement is getting removed from the release. If you would like to file an exception please see https://github.com/kubernetes/sig-release/blob/master/releases/EXCEPTIONS.md /milestone clear |
One use case for this: kubernetes-sigs/jobset#27 |
/stage alpha |
I don't think this enhancement is big enough to write a blog post, at least during the alpha stage. Maybe we'll want to have one in beta, but let us skip the blog post for this release. |
Hello @sanposhiho 👋, v1.29 Enhancements team here. Just checking in as we approach code freeze at 01:00 UTC Wednesday 1st November 2023 Here's where this enhancement currently stands:
Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. With all this, the status of this KEP is As always, we are here to help if any questions come up. Thanks! |
@AnaMMedina21 We already merged the PR necessary for this enhancement. |
@sanposhiho In the Issue Description can you update the KEP link to the latest link? The link broke when it got renamed from |
Hello @sanposhiho 👋, 1.29 Enhancements team here. With all the implementation(code related) PRs merged as per the issue description, this enhancement is now marked as The test freeze is 01:00 UTC Wednesday 15th November 2023 / 18:00 PDT Tuesday 14th November 2023. Please make sure all test PRs are merged in by then. Let me know if there are any test PRs we should track. Thanks! |
@sanposhiho is there a similar enhancement planned to add MatchLabelKeys/mismatchLabelKeys to the PodDisruptionBudgetSpec as well? |
That doesn't sound possible, as there is no Pod to get the keys from. |
@kubernetes/sig-scheduling-leads Can we make it beta in this release? If Yes, can anyone |
/label lead-opted-in |
Hello 👋 1.30 Enhancements Lead here, I'm closing milestone 1.29 now, /milestone clear |
Hello @sanposhiho 👋, 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 Here's where this enhancement currently stands:
For this KEP, we would just need to update the following:
The status of this enhancement is marked as |
@Huang-Wei can you? 🙏 |
/milestone v1.30 |
With #4450 being merged, this Enhancements can now be marked as |
Hi @sanposhiho, 👋 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. |
Hello @sanposhiho 👋, v1.30 Docs Shadow here. Does this enhancement work planned for v1.30 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against Also, take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release. Thank you! I see this being promoted to beta in v1.30. Please update the issue description to reflect the beta changes and ✔️ the alpha changes section. I don't see any PR in the docs website linking to this issue (in issue activity history), so marking this as "Need Docs". At minimum, we'll need a feature bump docs PR (If there are no logical changes). Thanks! |
@natalisucks @Vyom-Yadav |
Hey again @sanposhiho 👋 Enhancements team here, Just checking in as we approach code freeze at 02:00 UTC Wednesday 6th March 2024 . Here's where this enhancement currently stands:
For this enhancement, I couldn't find any (open) PRs in k/k. With this, it is now marked as Please let me know if there are other PRs in k/k we should be tracking for this KEP. |
kubernetes/kubernetes#123638 is the only one necessary for this beta graduation, thanks. |
Hello @sanposhiho 👋 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 If you still wish to progress this enhancement in /milestone clear |
@kubernetes/sig-scheduling-leads |
/label lead-opted-in |
Enhancement Description
MatchLabelKeys
to Pod Affinity and Pod Anti AffinityMatchLabelKeys
(the same one as Pod Topology Spread) toPodAffinityTerm
kubernetes#112947k/enhancements
) update PR(s):MatchLabelKeys
to PodAffinity and PodAntiAffinity #3651k/k
) update PR(s):k/website
) update PR(s):k/enhancements
) update PR(s): KEP-3633: graduate matchLabelKeys/mismatchLabelKeys to beta #4450k/k
) update PR(s): graduate MatchLabelKeysInPodAffinity to Beta kubernetes#123638k/website
) update(s): graduate MatchLabelKeysInPodAffinity to beta website#45181Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
/sig scheduling
/assign
The text was updated successfully, but these errors were encountered: