Kubernetes just dropped the Node Readiness Controller - a smarter way to track node health. It slaps taints on nodes based on custom signals, not just the plain old "Ready" status. The goal? Safer pod scheduling that actually reflects what’s going on under the hood.
It's powered by the NodeReadinessRule (NRR) API, which lets operators define custom rules tied to real infrastructure signals. Think of it as a DIY control panel for taints and node readiness.
