enhancements
enhancements copied to clipboard
kubernetes
Graceful Leader Transition
Enhancement Description
Allow leader elected components to transition to a follower state without restarting the process
- One-line enhancement description (can be used as a release note):
- Kubernetes Enhancement Proposal:
- Discussion Link:
- Primary contact (assignee): @Jefftree
- Responsible SIGs: sig api-machinery
- Enhancement target (which target equals to which milestone):
- Alpha release target (x.y): 1.34
- Beta release target (x.y):
- Stable release target (x.y):
- [ ] Alpha
- [x] KEP (
k/enhancements) update PR(s): https://github.com/kubernetes/enhancements/pull/5367 - [ ] Code (
k/k) update PR(s): - [ ] Docs (
k/website) update PR(s):
- [x] KEP (
Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
Hello @Jefftree 👋, v1.34 Enhancements team here.
Just checking in as we approach Enhancements Freeze on 21:00 UTC Friday 20th June 2025. (That's tomorrow)
This enhancement is targeting stage alpha for v1.34 (correct me, if otherwise)
Here's where this enhancement currently stands:
- [X] KEP readme using the latest template has been merged into the k/enhancements repo.
- [X] KEP status is marked as
implementableforlatest-milestone: v1.34. - [X] KEP readme has up-to-date graduation criteria
- [x] KEP has a production readiness review that has been completed and merged into k/enhancements. (For more information on the PRR process, check here). If your production readiness review is not completed yet, please make sure to fill the production readiness questionnaire in your KEP by the PRR Freeze deadline so that the PRR team has enough time to review your KEP.
For this KEP, we would just need to update the following:
- PRR completed and merged
The status of this enhancement is marked as At risk for enhancements freeze. Please keep the issue description up-to-date with appropriate stages as well.
If you anticipate missing enhancements freeze, you can file an exception request in advance. Thank you!
Hi @stmcginnis, PRR should have already been completed https://github.com/kubernetes/enhancements/blob/master/keps/prod-readiness/sig-api-machinery/5366.yaml.
Hello @Jefftree 👋, 1.34 Docs Lead here.
Does this enhancement work planned for 1.34 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.34 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 3rd July 2025 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!
Hi @Jefftree 👋 -- this is Mélony (@cloudmelon) from the 1.34 Communications Team! For the v1.34 release, we are currently in the process of collecting and curating a list of potential feature blogs, and we'd love for you to consider writing one for your enhancement! As you may be aware, feature blogs are a great way to communicate to users about features which fall into (but not limited to) the following categories:
- This introduces some breaking change(s)
- This has significant impacts and/or implications to users
- ...Or this is a long-awaited feature, which would go a long way to cover the journey more in detail 🎉 To opt in to write a feature blog, could you please let us know and open a "Feature Blog placeholder PR" (which can be only a skeleton at first) against the website repository by Friday 11th July? For more information about writing a blog, please find the blog contribution guidelines 📚
[!Tip] Some timeline to keep in mind:
- 02:00 UTC Friday 11th July 2025: Feature blog PR freeze
- Friday 8th August 2025: Feature blogs ready for review
- You can find more in the release document
[!Note] In your placeholder PR, use
XXcharacters for the blogdatein 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 @Jefftree 👋, 1.34 Docs Lead here.
Does this enhancement work planned for 1.34 require any new docs or modification to existing docs? If so, please follows the steps here to open a PR against dev-1.34 branch in the k/website repo. This PR can be just a placeholder at this time and must be created before Thursday 3rd July 2025 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!
Just a reminder to open a placeholder PR against dev-1.34 branch in the k/website repo for this (steps available here) for this KEP if it requires new or modifications to existing docs:
The deadline for this is Thursday July 3 at 18:00 PDT. Thanks! 🚀
Hi @Jefftree 👋, v1.34 Communications Team here again!
This is a gentle reminder for the feature blog deadline mentioned above, which is 02:00 UTC Friday 11th July. To opt in, please let us know and open a Feature Blog placeholder PR against k/website by the deadline. If you have any questions, please feel free to reach out to us!
[!Tip] Some timeline to keep in mind:
- 02:00 UTC Friday 11th July 2025: Feature blog PR freeze
- Friday 8th August 2025: Feature blogs ready for review
- You can find more in the release document
[!Note] In your placeholder PR, use
XXcharacters for the blogdatein 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.
Hey again @Jefftree, 👋 v1.34 Enhancements team here,
Just checking in as we approach code freeze at 02:00 UTC Friday 25th July 2025.
Here's where this enhancement currently stands:
- [ ] All PRs to the Kubernetes repo that are related to your enhancement are linked in the above issue description (for tracking purposes).
- [ ] All PRs are ready to be merged (they have
approvedandlgtmlabels applied) by the code freeze deadline. This includes tests.
If the implementation work for this enhancement is occurring out-of-tree (i.e., outside of k/k), please link the relevant PRs in the issue description for visibility.
Alternatively, if you're unable to provide specific PR links, a confirmation that all out-of-tree implementation work is complete and merged will help us finalize tracking and maintain accuracy.
The status of this enhancement is marked as At risk for code freeze.
If you anticipate missing code freeze, you can file an exception request in advance.
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!
/milestone clear
Per discussion with @Jefftree, we're focusing on foundational controller improvements this cycle which do not require a feature gate (they're effectively bug fixes to existing behavior). In the future, feature gated changes are expected, but they won't land this release. As such, we don't need to track this enhancement for this release.
Hi @Jefftree :wave:, v1.35 Enhancements Lead here.
I am closing the v1.34 milestone now.
If you'd like to work on this enhancement in v1.35, please have the SIG lead opt-in by adding the lead-opted-in label, which ensures it gets added to the tracking board. Also, please set the milestone to v1.35 using /milestone v1.35.
Thanks!
/remove-label lead-opted-in /remove-label tracked/yes
Hi @jpbetz v1.35 Enhancements Lead here. It's too late to add any new KEP for v1.35, as we've stopped the Enhancements board syncing after the PRR freeze, which is a hard deadline starting from this release cycle. Read more on this here: https://github.com/kubernetes/sig-release/blob/master/releases/release_phases.md#prr-freeze
It's too late to add any new KEP for v1.35, as we've stopped the Enhancements board syncing after the PRR freeze, which is a hard deadline starting from this release cycle. Read more on this here: kubernetes/sig-release@
master/releases/release_phases.md#prr-freeze
OK, good to know.
Not a problem. This enhancement is not progressing this cycle.
/milestone clear