Graceful Leader Transition

[Jefftree]

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: https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/5366-graceful-leader-transition
• 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.36
  • Beta release target (x.y): 1.37
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): [KEP-5366] Graceful Leader Transition #5367 & KEP:5366: Graceful leader transition update feature gates #5865
  • Code (k/k) update PR(s): controller-manager: Add ControllerManagerReleaseLeaderElectionLockOnCancel feature gate kubernetes#136279
    • kube-controller-manager: Refactor leader election management to prepare for releasing lock on exit kubernetes#132620
    • controller-manager: Add ControllerManagerReleaseLeaderElectionLockOnCancel feature gate kubernetes#136279
    • kcm: Link the leader election release on exit feature gate kubernetes#137708
  • Docs (k/website) update PR(s): [KEP-5366] Add ControllerManagerReleaseLeaderElectionLockOnExit feature gate docs website#54706
• Beta
  • KEP (k/enhancements) update PR(s): KEP-5366: beta graduation for ControllerManagerReleaseLeaderElectionLockOnExit #6142
  • Code (k/k) update PR(s): [WIP] leaderelection: release lease only after OnStartedLeading returns kubernetes#139504
  • Docs (k/website) update(s):

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

[Jefftree]

/sig api-machinery
/cc @jpbetz

[deads2k]

/stage alpha
/label lead-opted-in
/milestone v1.34

[stmcginnis]

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:

• KEP readme using the latest template has been merged into the k/enhancements repo.
• KEP status is marked as implementable for latest-milestone: v1.34.
• KEP readme has up-to-date graduation criteria
• 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!

[Jefftree]

Hi @stmcginnis, PRR should have already been completed https://github.com/kubernetes/enhancements/blob/master/keps/prod-readiness/sig-api-machinery/5366.yaml.

[michellengnx]

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!