-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Retry Generate Name #4420
Comments
/sig api-machinery |
/label lead-opted-in |
Hello @jpbetz 👋, Enhancements team here. Just checking in as we approach enhancements freeze on Friday, February 9th, 2024 at 02:00 UTC. This enhancement is targeting for stage 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 |
With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀 |
Hi @jpbetz, 👋 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 @jpbetz 👋, 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 the new |
Draft Documentation PR: kubernetes/website#45154 |
Hey again @jpbetz 👋 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:
Everything looks good. Please let me know if there are any other PRs in k/k we should be tracking for this issue, other than kubernetes/kubernetes#122887. |
/milestone v1.31 |
With #4592 merged, we should update the issue description. |
@jpbetz Could I please get clarification on something. I see that in the upstream code for Alpha (PR https://github.com/kubernetes/kubernetes/pull/122887/files), the feature gate that was added was named as |
Hi @jpbetz 👋, 1.31 Docs Shadow here. Does this enhancement work 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 familiarized with the docs requirement for the release. Thank you! Daniel |
Hi @jpbetz 👋 from the v1.31 Communications Team! We'd love for you to opt in to write a feature blog about your enhancement! 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 |
Hi @jpbetz 👋, Just a reminder to open a placeholder PR against dev-1.31 branch in the k/website repo for this (steps available here). The deadline for this is a week away at Thursday June 27, 2024 18:00 PDT. Thanks, Daniel |
@jpbetz , friendly reminder about the upcoming blog opt-in and placeholder deadline on July 3rd. Please open a blog placeholder PR if you are interested in contributing a blog. |
Thanks, @hailkomputer I've created kubernetes/website#47022 |
Hey again @jpbetz 👋, 1.31 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. Here's where this enhancement currently stands:
With all the implementation(code related) PRs merged as per the issue description: Additionally, please let me know if there are any other PRs in k/k not listed in the description that we should track for this KEP, so that we can maintain accurate status. This enhancement is now marked as |
/milestone v1.32 |
/label lead-opted-in |
Hello @jpbetz 👋, 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:
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 |
Hello @jpbetz, 👋🏼 this is Edith from the v1.32 Communications Team! We’d love for you to consider writing a feature blog about your enhancement! ✍ 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. 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. |
Hello @jpbetz 👋, this is Anshuman, 1.32 Docs Shadow here. |
Hello @jpbetz! 🙂 👋 This is a reminder to author your feature blog post! 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. Thank you very much! |
Hello @jpbetz 👋, Enhancements team here (again 😁 ) With all the implementation(code related) PRs merged as per the issue description: This enhancement is now marked as Please note that KEPs targeting |
Thanks for the reminder! With the introduction of emulation versions, we do need to start keeping feature gates in code for 3 additional releases after promotions to stable. Who on the release team should we talk to about changing this guidance to prevent contributors from removing feature gates too soon? |
Hey @jpbetz! I'm one of the release team subproject owners. This feels out of scope for the release team. Updating the guidance around feature gate removal would belong to SIG Architecture, imo (either the Enhancements subproject or PRR). However, we're happy to help you publicize an update in that guidance either in the form of a feature blog for the release or an email to dev. CCing the current Release Comms lead in case you want a feature blog: @mbianchidev |
Thanks for mentioning me, Kat! @jpbetz in case you want to write a blog you can find all the guidelines in the upper comment that Edith left on this very issue! For anything else, e.g. a specific mention on the final release blog, let me know and we can work on that too. |
Enhancement Description
k/enhancements
) update PR(s): KEP-4420: Retry Generate Name #4421k/k
) update PR(s): Implement KEP-4420: Retry Generate Name kubernetes#122887k/website
) update PR(s): Document NameGenerationRetries feature gate website#45154k/enhancements
) update PR(s): KEP-4420: Promote retry generate name to beta #4592k/k
) update PR(s): Promote RetryGenerateName to beta kubernetes#124673k/website
) update(s): KEP-4420: Retry Generate Name: Promote to beta website#46983k/enhancements
) update PR(s): KEP-4420: Promote RetryGenerateName to GA in 1.32 #4821k/k
) update PR(s): Promote RetryGenerateName to GA kubernetes#127093k/website
) update(s): Promote RetryGenerateName to GA in 1.32 website#47770Please 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: