What is the problem that your customer is facing?

Right now it is possible to define a nodeSelector for fluentd daemonSets via .spec.collection.logs.fluentd.nodeSelector in ClusterLogging, however, more complex affinity rules such as the following is not currently possible:
 {{ affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:

• matchExpressions:
• key: node-role.kubernetes.io/worker
  operator: Exists
• key: node-role.kubernetes.io/infra
  operator: DoesNotExist}}
  P.S.1: This can be also added to other components (es, kibana, .. ) as well.
  P.S.2: I'm willing to contribute a PR for this if the feature matches the project guidelines.

  What is the business impact, if any, if this request will not be made

available?
<<Please detail any impact on the 'what happens if not delivered' so that
we can better make judgement of the priority for this request.>>

What are your expectations for this feature

<<Please add any requirements you may have so that we are able to deliver
what you need.>>

Have you done this before and/or outside of support and if yes, how?

(Optional)
<<Please add any information on how you have done that so far or any ideas
you'd like to share with us.>>