Kubernetes v1.37 introduces five standardized Node lifecycle conditions to provide a consistent, native way to represent node states such as draining, maintenance, and graceful shutdown. These conditions replace fragmented, provider-specific reporting mechanisms by utilizing the standard Node status API with machine-readable reasons and messages. The feature is currently behind the alpha NodeLifecycleConditions feature gate.
Key points
Five new node conditions have been introduced to standardize maintenance and lifecycle reporting: DrainInProgress, Drained, MaintenancePlanned, MaintenanceInProgress, and GracefulNodeShutdownInProgress.
Standardized conditions allow for uniform status tracking across different cluster environments and tooling.
The new API uses standard Kubernetes condition fields (status, reason, message) to enable both automated controller logic and human-readable reporting.
The NodeLifecycleConditions feature is an alpha implementation in v1.37, requiring an explicit feature gate to enable.