Node Affinity selectors use "AND" instead of "OR" logic

[ravindk89]

Using latest stable Operator:

Attempted to apply node selectors as follows:

for node 2 -> 5

This results in the following YAML:

  pools:
  - affinity:
      nodeAffinity:
        requiredDuringSchedulingIgnoredDuringExecution:
          nodeSelectorTerms:
          - matchExpressions:
            - key: kubernetes.io/hostname
              operator: In
              values:
              - node2
            - key: kubernetes.io/hostname
              operator: In
              values:
              - node3
            - key: kubernetes.io/hostname
              operator: In
              values:
              - node4
            - key: kubernetes.io/hostname
              operator: In
              values:
              - node5

This fails scheduling as Kubernetes appears to look for hostnames with all of those labels at once, not just any single one

The correct YAML via @pjuarezd is:

 pools:
  - affinity:
      nodeAffinity:
        requiredDuringSchedulingIgnoredDuringExecution:
          nodeSelectorTerms:
          - matchExpressions:
            - key: kubernetes.io/hostname
              operator: In
              values:
              - node2
              - node3
              - node4
              - node5

I think the reasonable expectation here is to either:

• Convert the selector field to be a manual entry or pickbox for "or" semantics, or
• Treat the entire list like one giant "or"

The current functionality I think would not suffice for something like "restrict this tenant to the following node hostnames." It would work if you just applied a label I suppose.

[cniackz]

Reproduced this issue, thanks for reporting it.
To reproduce this issue, you have to go into Pod Placement when creating a Tenant: