Retry Generate Name

[jpbetz]

Enhancement Description

• One-line enhancement description (can be used as a release note): Create requests using generateName are retried automatically by the apiserver when the generated name conflicts with an existing resource name, up to a max limit of 7 retries.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/4420-retry-generate-name/README.md
• Discussion Link:
• Primary contact (assignee):
• Responsible SIGs:
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.30
  • Beta release target (x.y): 1.31
  • Stable release target (x.y): 1.32
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-4420: Retry Generate Name #4421
  • Code (k/k) update PR(s): Implement KEP-4420: Retry Generate Name kubernetes#122887
  • Docs (k/website) update PR(s): Document NameGenerationRetries feature gate website#45154
• Beta
  • KEP (k/enhancements) update PR(s): KEP-4420: Promote retry generate name to beta #4592
  • Code (k/k) update PR(s): Promote RetryGenerateName to beta kubernetes#124673
  • Docs (k/website) update(s): KEP-4420: Retry Generate Name: Promote to beta website#46983
• Stable
  • KEP (k/enhancements) update PR(s): KEP-4420: Promote RetryGenerateName to GA in 1.32 #4821
  • Code (k/k) update PR(s): Promote RetryGenerateName to GA kubernetes#127093
  • Docs (k/website) update(s): Promote RetryGenerateName to GA in 1.32 website#47770

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

[jpbetz]

/sig api-machinery

[jpbetz]

/label lead-opted-in
/milestone v1.30

[tjons]

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 alpha for 1.30 (correct me, if otherwise)

Here’s where this enhancement currently stands:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: { CURRENT_RELEASE }. KEPs targeting stable will need to be marked as implemented after code PRs are merged and the feature gates are removed.
• KEP readme has up-to-date graduation criteria.
• KEP has submitted a production readiness review request for approval and has a reviewer assigned.
• KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here).

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!

[tjons]

With all the requirements fulfilled this enhancement is now marked as tracked for the upcoming enhancements freeze 🚀

[kcmartin]

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.
The placeholder PR deadline is 27th February, 2024.
Here's the 1.30 Release Calendar