-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Add Pod Index Label for StatefulSets and Indexed Jobs #4017
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
Comments
/sig apps |
/label beta |
@soltysh: The label(s) 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. |
/stage beta |
Hi @danielvegamyhre 👋, Enhancements team here! Just checking in as we approach enhancements freeze on 01:00 UTC Friday, 16th June 2023. This enhancement is targeting for stage Here's where this enhancement currently stands:
It looks like #4019 will address some of these requirements. For this KEP, we would just need to update the following:
The status of this enhancement is marked as |
@Atharva-Shinde this is only pending PRR review |
Ack. We'll mark this as tracked after it is approved. |
Looks like the PRR is approved and #4019 has gone in so this is now |
Hello @danielvegamyhre! 1.28 Docs Shadow here. Does this enhancement work planned for 1.28 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! |
Hey again @danielvegamyhre 👋 Just checking in as we approach Code freeze at 01:00 UTC Friday, 19th July 2023 . Here’s the enhancement’s state for the upcoming code freeze:
For this enhancement, it looks like the following code related PR/s are open and they need to be merged or should be in merge-ready state before the code freeze commences :
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! |
Hey @danielvegamyhre , could you please create a docs PR even if it is a draft PR with no content yet against dev-1.28 branch in the k/website repo. The deadline to create this draft PR is Thursday 20th July 2023. |
@Rishit-dagli Docs PR created here: kubernetes/website#42059 |
Hey @danielvegamyhre 👋 Enhancements Lead here With all the implementation(code related) PRs merged as per the issue description: This enhancement is now marked as |
All items for beta in 1.28 release have been completed. |
Hello 👋, 1.29 Enhancements Lead here. If you wish to progress this enhancement in v1.29, please have the SIG lead opt-in your enhancement by adding the /remove-label lead-opted-in |
@soltysh It looks like @alaypatel07 is eager to work on this for 1.32. Can we get a lead-opt-in for this feature? I think we can promote this to stable in this release. |
/label lead-opted-in |
Hello @alaypatel07 👋, v1.32 Enhancements team here. Just checking in as we approach enhancements freeze on 02:00 UTC Friday 11th October 2024 / 19:00 PDT Thursday 10th October 2024. This enhancement is targeting for stage Here's where this enhancement currently stands:
For this KEP, we would need to update the following:
Also, in the KEP readme, please make sure you update Release Signoff Checklist where applicable. Second If there are any questions in the KEP readme file that doesn’t apply to your KEP, please reply to them with NA if haven’t already and dont leave them blank. The status of this enhancement is marked as If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you! |
With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀 |
Hello @alaypatel07 and @danielvegamyhre 👋, 1.32 Docs Shadow here. |
Hello @alaypatel07 @danielvegamyhre 👋 from the v1.32 Communications Team! To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024. For more information about writing a blog see the blog contribution guidelines. |
Hello @alaypatel07 and @danielvegamyhre 👋, Just a reminder to open a placeholder PR against dev-1.32 branch in the k/website repo for this (steps available here). The deadline for this is 4 days away at Thursday October 24, 2024 18:00 PDT. Thanks, |
Hello @alaypatel07, this is a reminder for the feature blog post for v1.32. To opt-in, let us know and open a Feature Blog placeholder PR against the website repository by 30th Oct 2024. For more information about writing a blog see the blog contribution guidelines. Please reach out if you have any questions! |
@rashansmith @michellengnx apologies for delayed response, but I dont think a blog post is needed for this feature. |
Hello @danielvegamyhre @alaypatel07 👋, Enhancements team here (again 😁 ) Just checking in as we approach code freeze at 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024. Here’s where this enhancement currently stands:
For this enhancement, it looks like the following PRs need to be merged before code freeze (and we need to update the Issue description to include all the related PRs of this KEP if missing): If you anticipate missing code freeze, you can file an exception request in advance. Also, please let me know if there are other PRs in k/k we should be tracking for this KEP. |
Hello @danielvegamyhre @alaypatel07 👋, Enhancements team here. With all the implementation(code related) PRs merged as per the issue description:
This enhancement is now marked as Please note that KEPs targeting |
@alaypatel07 can you make sure the docs PR gets merged kubernetes/website#48496 |
/wg batch |
Hi @danielvegamyhre @alaypatel07 👋 , 1.33 Enhancements lead here, Now that this KEP has graduated to |
/remove-label lead-opted-in |
opened a PR for that: #5086 |
Uh oh!
There was an error while loading. Please reload this page.
Enhancement Description
Note: We will release the feature directly in Beta state since there is no benefit in having an alpha release, since we are simply adding a new label so there is very little risk (unlike removing an
existing label which other things may depend on, for example).
k/enhancements
) update PR(s): KEP-4017: Pod Index Label for StatefulSets and Indexed Jobs #4019k/k
) update PR(s):k/website
) update(s):k/enhancements
) update PR(s): KEP-4017: promote Pod Index Label for StatefulSets and Indexed Jobs to GA #4865k/k
) update PR(s):[KEP-4017]: update e2e and integration test for PodIndexLabel kubernetes#128107
Promote PodIndexLabel for Statefulset and IndexedJob stable kubernetes#128387
k/website
) update(s): [KEP 4017]: add documentation for PodIndexLabel going GA website#48496Please 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: