⚠️ Remove per node-data from rule status#131
⚠️ Remove per node-data from rule status#131Karthik-K-N wants to merge 1 commit intokubernetes-sigs:mainfrom
Conversation
✅ Deploy Preview for node-readiness-controller ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: Karthik-K-N The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
9be2c6d to
a0c2b84
Compare
|
Thanks @Karthik-K-N , I'll get to it this week. |
| "node", node.Name, "rule", rule.Name) | ||
| // Continue with other rules even if one fails | ||
| r.recordNodeFailure(rule, node.Name, "EvaluationError", err.Error()) | ||
| r.recorder.Eventf(node, corev1.EventTypeWarning, "RuleEvaluationError", "Failed to evaluate rule for node: %v", err) |
There was a problem hiding this comment.
cc @Priyankasaggu11929 This PR introduces event recorder and some node eventing which may be related to #134
|
@Karthik-K-N This direction looks good to me. As we discussed, we need to plan for a scalability test before spending much of the effort in refactoring and api reshaping. |
sure will do. |
Description
This PR updates the NRR CRD status filed to remove the per-node related data.
Related Issue
Fixes #111
Type of Change
/kind api-change
Testing
Checklist
make testpassesmake lintpassesDoes this PR introduce a user-facing change?
Doc #(issue)