Repository navigation
Remove per node-data from rule.status #111
Description
Following up on #89, we likely are shooting ourselves in the foot, with concurrent node-updates in the node.
We are planning for scalability tests #(TODO: capture issue here) for upto 1k, 2k and 5k nodes with kwok, to assess our goals for scale. This issue is to track removing node-references from rule.status object following sig-arch api-conventions
Goal:
- Remove per node-data from status -- delete AppliedNodes, FailedNodes, and NodeEvaluations from NodeReadinessRuleStatus.
- Instead of NodeEvaluations, emit K8s Events / metrics when significant actions occur for history / audit.
/kind api-change
Activity
ajaysundark commentedon Jan 25, 2026
cc @AvineshTripathi @Karthik-K-N
Karthik-K-N commentedon Jan 27, 2026
/assign
k8s-triage-robot commentedon Apr 27, 2026
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle stale/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Karthik-K-N commentedon Apr 27, 2026
/remove-lifecycle stale
ajaysundark commentedon Jul 9, 2026
/remove-lifecycle stale
feat(plugin): derive node state from taints rather than rule status