KEP-6371keps/sig-node/6371-external-node-liveness-detection
External Node Liveness Detection
This KEP makes node liveness detection replaceable with a custom implementation. A cluster operator can turn off the detector built into the node lifecycle controller, disable kubelet Lease heartbeats, and supply an external detector that writes Ready=Unknown. The node lifecycle controller retains responsibility for all other lifecycle management, such as ev… Full summary
This KEP makes node liveness detection replaceable with a custom implementation. A cluster operator can turn off the detector built into the node lifecycle controller, disable kubelet Lease heartbeats, and supply an external detector that writes Ready=Unknown. The node lifecycle controller retains responsibility for all other lifecycle management, such as eviction and zone disruption handling. This is implemented by a --node-liveness-source=external flag on the kube-controller-manager, which stops the controller from checking liveness and changes how it reacts to Ready=Unknown when the condition is written by an external node liveness detector. An enableNodeLease: false field is added to the kubelet for configurations that do not need node lease heartbeats.
Facts
- Authors
- @jpbetz
- Approvers
- @mrunalp
- Reviewers
- @mrunalp
- PRR approvers
- @johnbelamaricalpha
- Tracking issue
- #6371(opens GitHub in a new tab) openmilestone v1.38sig/nodestage/alphatracked/yeskind/keplead-opted-in
- Milestones
- alpha v1.38
- Participating SIGs
- sig-scalabilitysig-cloud-providersig-api-machinery
- Feature gates
- ExternalNodeLivenessDetection
- Created / last updated
- 2026-09-14 / none