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
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:
/kind api-change