At the moment it is not possible to configure a pod affinity for the config-listener.

As a user I want to have the ability to specify the OCP Nodes on which the config-listener Pods can run, either via nodeSelector or nodeAffinity settings.

Implementation Idea

It should be possible to use the existing SchedulingSpec struct as a field in the ConfigListenerSpec so that users can specify affinity, priorityClassName, tolerations and tolopologySpreadConstraints for the config-listener pod.

Users would then configure affinity settings as follows:

spec: 
  configListener: 
    scheduling: 
       affinity: 
        ....