[k8s API machinery] Exception Request for KEP-4355

[Jeffrey Ying]

Hi everyone!

I'd like to request an exception for a KEP for 1.31.

• Enhancement name: Coordinated Leader Election
• Enhancement status (alpha/beta/stable): alpha
• SIG: api-machinery
• k/enhancements repo issue #: 4355 (https://github.com/kubernetes/enhancements/issues/4355)
• PR #’s: https://github.com/kubernetes/kubernetes/pull/124012
• Additional time needed (in days): 2 day
• Reason this enhancement is critical for this milestone: 

Feature improves upgrade reliability by providing deterministic leader selection during mixed version states. This is an anticipated feature addressing a version skew issue during upgrades.

• Risks from adding code late: (to k8s stability, testing, etc.)

Low risk as feature is gated going into alpha with gate turned off and new types disabled by default.

• Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.)

Coordinated Leader Election provides deterministic leader election during upgrades to satisfy Kubernetes version skew. Delaying will push back the timeline to reach customers. See more details in the KEP.

Code is in a ready to merge state at the moment. Requesting for 2 days because I am OOO today if there are any issues with merging.

Thanks,

Jeffrey

[Joe Betz]

I support this as a SIG API Machinery TL.  The risk is low due to this being a well isolated off-by-default alpha feature.  This one only missed the deadline by ~hrs due to some test failure that needed to be addressed.

--
You received this message because you are subscribed to the Google Groups "K8s API Machinery SIG" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-api-m...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-api-machinery/CANZyWOQnE6cc-HAsZ4AZKPT%3DWC%2BN2b5UWNpz_gEWhyF8GCeEkw%40mail.gmail.com.