✨ Add nodereadinessrulereport CRD and controller

[Karthik-K-N]

Description

This PR creates nodereadinessrulereport CRD and controller

# kubectl get nrrp
NAME                                NODE                     MATCHED RULES   UNMATCHED RULES   APPLIED TAINTS   ERRORS   AGE
nrr-report-nrr-test-control-plane   nrr-test-control-plane   0               1                 0                0        82s
nrr-report-nrr-test-worker          nrr-test-worker          0               1                 1                0        82s
nrr-report-nrr-test-worker2         nrr-test-worker2         0               1                 1                0        82s


# kubectl apply -f examples/cni-readiness/network-readiness-rule.yaml
nodereadinessrule.readiness.node.x-k8s.io/network-readiness-rule unchanged


# kubectl get nrrp
NAME                                NODE                     MATCHED RULES   UNMATCHED RULES   APPLIED TAINTS   ERRORS   AGE
nrr-report-nrr-test-control-plane   nrr-test-control-plane   0               1                 0                0        3m33s
nrr-report-nrr-test-worker          nrr-test-worker          1               0                 0                0        3m33s
nrr-report-nrr-test-worker2         nrr-test-worker2         1               0                 0                0        3m33s


# kubectl get nrrp nrr-report-nrr-test-worker2 -o yaml
apiVersion: readiness.node.x-k8s.io/v1alpha1
kind: NodeReadinessRuleReport
metadata:
  creationTimestamp: "2026-02-20T13:05:33Z"
  generation: 1
  name: nrr-report-nrr-test-worker2
  ownerReferences:
  - apiVersion: v1
    blockOwnerDeletion: true
    controller: true
    kind: Node
    name: nrr-test-worker2
    uid: 8701cb81-06fa-4e92-9d82-5de9d6ef0c99
  resourceVersion: "1671"
  uid: db8a7abb-ecc0-4a6d-93f5-97ca3cbc6f53
spec:
  nodeName: nrr-test-worker2
status:
  readinessReports:
  - lastEvaluationTime: "2026-02-20T13:09:38Z"
    message: Node successfully matches all rule criteria.
    reason: CriteriaMet
    ruleName: network-readiness-rule
    ruleStatus: Matched
    taintStatus: Absent
  summary:
    appliedTaints: 0
    errors: 0
    matchedRules: 1
    unMatchedRules: 0

Related Issue

Fixes #89

Type of Change

Testing

Checklist

• make test passes
• make lint passes

Does this PR introduce a user-facing change?

Create nodereadinessrulereport CRD and controller

Doc #(issue)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Karthik-K-N
Once this PR has been reviewed and has the lgtm label, please assign ajaysundark for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for node-readiness-controller canceled.

Name	Link
🔨 Latest commit	598570f
🔍 Latest deploy log	https://app.netlify.com/projects/node-readiness-controller/deploys/69985df53fbb1a00089bf229

[ajaysundark]

Not strongly opinionated, but does NodeReadinessEvaluation (since this is extracting out NodeEvaluation from rule.status) a better fit for name?

[Karthik-K-N]

sure, thats looks good too.

[ajaysundark]

wouldn't this new array of objects in NodeReadinessRuleReport affect scalability as that could exceed 1.5MB? It seem to me that we are moving the problem around. IMO, the evaluation results should be independent CRs not listed below a uber struct.

but it feels like we should really find where the burden is before refactoring.

[Karthik-K-N]

My thought was given that we might have few rules and this report is per node. It should be good. But can explore more.

[ajaysundark]

ah okay, having this per node makes sense.

I'm still on it, I'll take a second look later this week.. have been juggling between few things

[Karthik-K-N]

Sure no issues, Thank you.