Epic Goal

...

Why is this important?

...

Scenarios

Ref:

https://redhat-internal.slack.com/archives/CTDEY6EEA/p1704361877592779

https://redhat-internal.slack.com/archives/GUWQE4D2N/p1701335584930869

Customer is looking for an operand  to be able to set some placement rule for all the cluster 4.x and. above or 4.x and less :

something like :

clusterSelector:
    matchExpressions:
      - key: openshiftVersion
        operator: Greater than or equal 
        values:
         -4.12 => this should match all 4.12, 4.13, 

Seems that is not possible with the existent operands.

Can more operands be added such as  (start with/ prefixed/include, greater than or equal etc ...) ? this could be very helpful for many use cases

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. ...

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.