Description of problem:
Currently the kubevirt-dpdk-checkup has 2 optional parameters for the nodelabelselector - one for each entity (DPDK VMI and traffic generator Pod):
1. DPDKNodeLabelSelector
2. trafficGeneratorNodeLabelSelector

If these parameters are not set, then the desired behavior is that the objects will prefer to be scheduled on different nodes.
This behavior is not yet implemented.

Version-Release number of selected component (if applicable):

How reproducible:
100%

Steps to Reproduce:
1. run kubevirt-dpdk-checkup without the DPDKNodeLabelSelector, trafficGeneratorNodeLabelSelector optional parameters.
2.
3.

Actual results:
there is no a pod anti-affinity that prefers to schedule the objects on different nodes

Expected results:
there is a pod anti-affinity that prefers to schedule the objects on different nodes.

Additional info: