search

kubernetes / enhancements

Enhancements tracking repo for Kubernetes
Apache License 2.0
3.39k stars 1.46k forks source link

Introduce `MatchLabelKeys` to Pod Affinity and Pod Anti Affinity #3633

Open sanposhiho opened 1 year ago

sanposhiho commented 1 year ago

Enhancement Description

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

/sig scheduling /assign

salehsedghpour commented 8 months ago

Hello πŸ‘‹ 1.30 Enhancements Lead here,

I'm closing milestone 1.29 now, Shall we add /milestone v1.30? Thanks!

/milestone clear

salehsedghpour commented 7 months ago

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 beta for v1.30 (correct me, if otherwise)

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 at risk for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well, I couldn't find any related PR regarding this KEP in k/enhancements. Thank you!

sanposhiho commented 7 months ago

Shall we add /milestone v1.30? Thanks!

@Huang-Wei can you? πŸ™

Huang-Wei commented 7 months ago

/milestone v1.30

salehsedghpour commented 7 months ago

With #4450 being merged, this Enhancements can now be marked as tracked for enhancements freeze

natalisucks commented 7 months ago

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. The placeholder PR deadline is 27th February, 2024.

Here's the 1.30 Release Calendar

Vyom-Yadav commented 7 months ago

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 dev-1.30 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday, February 22nd, 2024 18:00 PDT

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!

sanposhiho commented 6 months ago

@natalisucks I'll write the blog post for this release. https://github.com/kubernetes/website/pull/45182

@Vyom-Yadav Here it is: https://github.com/kubernetes/website/pull/45181

salehsedghpour commented 6 months ago

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 at risk for code freeze for the v1.30 Code Freeze!

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!

sanposhiho commented 6 months ago

@salehsedghpour

Please let me know if there are other PRs in k/k we should be tracking for this KEP.

https://github.com/kubernetes/kubernetes/pull/123638 is the only one necessary for this beta graduation, thanks.

salehsedghpour commented 6 months ago

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 v1.30 milestone.

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

/milestone clear

sanposhiho commented 4 months ago

@kubernetes/sig-scheduling-leads Can anyone add /label lead-opted-in, I'll work on this in the next release cycle too. We're just waiting for the api-reviews in - https://github.com/kubernetes/kubernetes/pull/123638

Huang-Wei commented 4 months ago

/label lead-opted-in

alculquicondor commented 4 months ago

/milestone v1.31

tjons commented 3 months ago

Hello @sanposhiho πŸ‘‹, 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 beta for 1.31 (correct me, if otherwise)

Here’s where this enhancement currently stands:

With all the KEP requirements in place and merged into k/enhancements, this enhancement is all good for the upcoming enhancements freeze. πŸš€

The status of this enhancement is marked as tracked for enhancement freeze. Please keep the issue description up-to-date with appropriate stages as well. Thank you!

sreeram-venkitesh commented 3 months ago

/stage beta

salaxander commented 3 months ago

Hello @sanposhiho πŸ‘‹, 1.31 Docs Shadow here.

Does the work for the 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!

sanposhiho commented 3 months ago

@salaxander Opened in - https://github.com/kubernetes/website/pull/45181

mbianchidev commented 3 months ago

Hey @sanposhiho

:wave: 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.

sanposhiho commented 3 months ago

@mbianchidev

Created an placeholder PR in - https://github.com/kubernetes/website/pull/46833

mbianchidev commented 2 months ago

@mbianchidev

Created an placeholder PR in - kubernetes/website#46833

Amazing! Let me know if you need anything now or later on :)

tjons commented 2 months ago

Hey again @sanposhiho πŸ‘‹ 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 .

I found one PR for this KEP in 1.31:

Here's where this enhancement currently stands:

With the above criteria met, this enhancement is now tracked for code freeze!

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!

sanposhiho commented 2 months ago

Thanks, you're right, that's the only one we need for this enhancement.