[FEATURE] Support anyOf condition aggregation policy alongside the existing allOf behavior

[vishnukothakapu]

Is your feature request related to a problem or existing issue? Please describe.

NRC evaluates conditions with implicit AND logic all conditions must pass before a taint is removed. That works for most cases, but I've hit a wall with it.

We have nodes that can boot with either a hardware GPU driver or a software fallback. If either is ready, the node should schedule GPU workloads. There's no clean way to express this today. Two rules with the same taint key hits the webhook conflict check. The only real escape is writing a sidecar to synthesize a third aggregated condition which is extra infrastructure just to paper over a gap in the rule API.

Didn't find this covered in existing issues. #272 is about rule ordering (different), #282 is about defaultStatus for missing conditions (also different).

Describe the solution you'd like

Add an optional conditionPolicy field allOf (default, existing behavior) or anyOf (taint removed when at least one condition is satisfied):

spec:
  conditionPolicy: anyOf
  conditions:
    - type: "gpu.example.com/HardwareDriverReady"
      requiredStatus: "True"
    - type: "gpu.example.com/SoftwareFallbackReady"
      requiredStatus: "True"
  taint:
    key: "readiness.k8s.io/GPUReady"
    effect: "NoSchedule"
  enforcementMode: "continuous"

[ajaysundark]

An anyOf optional behavior sounds useful.

My only concerns are that

1. It kinda breaks the homogeneity of the group of nodes evaluated by a rule.
2. It's not straightforward for the user to know what to expect of the node after bootstrap - how would cluster-operator will be able to reason about the node satisfying the declared readiness requirements?

I welcome you to discuss your use case further if you are available to bring this to one of our biweekly calls