Enhancement name:
Node Lifecycle Conditions
Enhancement status (alpha/beta/stable): Alpha
SIG: SIG-Node
k/enhancements repo issue #:
https://github.com/kubernetes/enhancements/issues/5683
PR #’s:
https://github.com/kubernetes/enhancements/pull/6161
Additional time needed (in calendar days, due end of day AoE): 1 day (Tuesday, June 16th). KEP is approved from Sig-node and has PRR approval, but needs addition time for an LGTM.
Reason this enhancement is critical for this milestone:
It's important to the ecosystem to establish a pattern that can be used for future expansion.
Risks from adding code late: (to k8s stability, testing, etc.):
There's no new API or behavior changes. The change establishes several "well-known" node conditions.
Risks from cutting enhancement: (partial implementation, critical customer usecase, etc.):
Introducing a new pattern to the Node will take several releases. Delaying in this release would further delay the ecosystem adoption and solving the use cases mentioned in the KEP.
Thank you,
-Ryan
--
You received this message because you are subscribed to a topic in the Google Groups "kubernetes-sig-release" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/kubernetes-sig-release/QWbB2eyPTKg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
kubernetes-sig-re...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/kubernetes-sig-release/ba65b1a2-77da-42ec-8bd2-292e49f9bc23n%40googlegroups.com.