Node Affinity adding

[eduard-netoplayltd]

Is your feature request related to a problem? Please describe.
So on my cluster i have nodes with public and private IP. And it will be great if you can add Node affinities to choose by node tag or/and label in values

Describe the solution you'd like
Just adding it like option will be enough like:

elementWeb:
  enabled: true
  additional: {}
  replicas: 1
  image:
    registry: ghcr.io
    repository:
    tag: <WEB_DOCKER_TAG>
    pullSecrets: 
      - name: github-auth
  ingress:
    host: <WEBHOST>
    annotations: {}
    tlsEnabled: true
    service: {}
  labels: {}
  extraEnv: []
  containersSecurityContext:
    allowPrivilegeEscalation: true
    capabilities:
      drop:
        - ALL
    readOnlyRootFilesystem: true
  podSecurityContext:
    fsGroup: 10004
    runAsGroup: 10004
    runAsNonRoot: true
    runAsUser: 10004
    seccompProfile:
      type: RuntimeDefault
    supplementalGroups: []
  resources:
    requests:
      memory: 50Mi
      cpu: 50m
    limits:
      memory: 200Mi
  serviceAccount:
    create: true
    name: ""
    annotations: {}
  tolerations: []
  topologySpreadConstraints: []
 PodAffinity[]
 NodeAffinity[]
 //     nodeAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            nodeSelectorTerms:
              - matchExpressions:
                  - key: role
                    operator: In
                    values:
                      - Private 
                    ```

[benbz]

Hi, thanks for the request, it seems like a reasonable one. It currently isn't high on our priority list, though we'd be happy to reconsider the priority of it on request from an ESS Pro customer.

In the mean time community PR would be welcome to implement this, however it would need to support all components and have appropriate tests to be accepted.

[xamindar]

This would be really useful to have. Affinity can not be patched in after pod is deployed so it really should be an option on the chart.

[somaz94]

I recently added per-component and global priorityClassName support in #1438 (merged), which wires the same value across the matrix-stack components.

I'd be happy to follow up with affinity here, plus nodeSelector and tolerations since those usually go together for scheduling, using the same per-component + global pattern so it stays consistent with what's already there.

Would you be open to a PR for that? If you'd rather keep the first pass to just affinity, I can scope it that way too.

[benbz]

I recently added per-component and global priorityClassName support in #1438 (merged), which wires the same value across the matrix-stack components.

I'd be happy to follow up with affinity here, plus nodeSelector and tolerations since those usually go together for scheduling, using the same per-component + global pattern so it stays consistent with what's already there.

Would you be open to a PR for that? If you'd rather keep the first pass to just affinity, I can scope it that way too.

We'd happily accept PRs for the different parts of affinity (nodeAffinity, podAffinity & podAntiAffinity). We've already got nodeSelector, tolerations and topologySpreadConstraint support so those aren't necessary. Given the request here is for nodeAffinity and the others haven't been explicitly requested, I'd prioritise that.

Good manifest test coverage is critical. Thanks