Coordinated Leader Election

[jpbetz]

Enhancement Description

• One-line enhancement description (can be used as a release note): A "coordinated" component leader election mechanism that is safer for upgrades and rollbacks.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/4355-coordinated-leader-election/README.md
• Discussion Link:
• Primary contact (assignee): @jpbetz
• Responsible SIGs: sig-apimachinery
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.30
  • Beta release target (x.y): 1.33
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-4355: Coordinated Leader Election #4356
  • Code (k/k) update PR(s):Coordinated Leader Election kubernetes#124012
  • Docs (k/website) update PR(s): [KEP-4355] Coordinated Leader Election alpha documentation website#46982
• Beta
  • KEP (k/enhancements) update PR(s): Coordinated Leader Election to Beta #5088
  • Code (k/k) update PR(s):
    • Add E2E tests for CLE kubernetes#130575
    • CLE: Remove invalid emulated version and add lexographical order test kubernetes#130735
    • Parallelize lease candidate ping kubernetes#130533
    • Add third party strategy to the coordinate leader election integratio… kubernetes#129973
    • [KEP-4355] Promote Coordinated Leader Election to Beta kubernetes#130751
  • Docs (k/website) update(s):
    • KEP 4355 - CoordinatedLeaderElection to Beta Docs  website#49950

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

This is targeting 1.31, but we'd like to merge the KEP early if possible so we can start implementation work.

[jpbetz]

/assign @sttts

[deads2k]

/milestone v1.31

[salehsedghpour]

/milestone clear