feat: add suspend field to NodeReadinessRuleSpec to pause rule evalua…

[vishnukothakapu]

Description

This PR introduces a suspend boolean field to the NodeReadinessRuleSpec. When a rule is suspended (suspend: true), the controller skips the reconciliation loop for that specific rule, leaving any existing taints and the cluster state exactly as they are. This provides a safe, standard mechanism to pause rule evaluation during maintenance windows or debugging, without needing to delete the rule.

Related Issue

Fixes #335

Type of Change

/kind feature
/kind api-change

Testing

• Added a unit test in nodereadinessrule_controller_test.go to explicitly verify that when suspend: true is set, the controller skips evaluation and does not append a finalizer.
• Regenerated CRD manifests and deepcopy functions.

Checklist

• make test passes
• make lint passes

Does this PR introduce a user-facing change?

Added `suspend` field to `NodeReadinessRuleSpec`. When `suspend: true` is set, the controller skips evaluation of the rule, effectively pausing taint management while preserving the current cluster state.

[netlify]

✅ Deploy Preview for node-readiness-controller canceled.

Name	Link
🔨 Latest commit	4632d31
🔍 Latest deploy log	https://app.netlify.com/projects/node-readiness-controller/deploys/6a724a224169bb00087dbdb2

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vishnukothakapu
Once this PR has been reviewed and has the lgtm label, please assign sergeykanzhelev 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

[kubernetes-prow]

Hi @vishnukothakapu. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Karthik-K-N]

Thanks for the PR, Given its a feature request and API change,I would recommend its always better to get consciousness about the proposed feature on the parent issue before proceeding with the PR, it generally saves duplicate work or time.

[vishnukothakapu]

Contributor

Thanks for the tip, @Karthik-K-N! You're right. I had some free time, so I thought I'd quickly prototype it to get a feel for how it would look. Going forward, I'll wait for consensus on the parent issue before spending time on implementation, so I don't end up working on something that might not be needed.

Once the parent issue is reviewed, I'd really appreciate any feedback on the implementation as well. Thanks!

[Karthik-K-N]

Contributor

Thanks for the tip, @Karthik-K-N! You're right. I had some free time, so I thought I'd quickly prototype it to get a feel for how it would look. Going forward, I'll wait for consensus on the parent issue before spending time on implementation, so I don't end up working on something that might not be needed.

Once the parent issue is reviewed, I'd really appreciate any feedback on the implementation as well. Thanks!

That is completely fair. Apologies for that, I thought the PR is ready for review, May be if you think its under experiment, feel free to mark it as Draft or WIP.