Kubernetes nodes report “Ready” before critical dependencies, such as CNI plugins, storage drivers or device plugins are fully functional. This “readiness gap” causes non-deterministic scheduling, where sensitive workloads immediately fail upon placement.

Since our KubeCon NA Unconference discussion, this initiative has matured into an official SIG-Node subproject. In this session, its maintainers will present the architecture of the Node Readiness Controller, which uses ‘NodeReadinessRules’ to declaratively manage taints based on custom conditions, ensuring a protected node initialization.

This session is designed for platform builders and contributors. We will discuss:
-Architecture patterns: Leveraging existing node-problem-detector ecosystem as a unified mechanism for readiness reporting.
-Roadmap: Discuss current status, upcoming features and potential integration pathways.
-Cross-SIG alignment: how the controller interacts with existing scheduling primitives and autoscalers.