Bug 2170437

Summary:	kubevirt-dpdk-checkup affinity not set to prefer the objects to run on different nodes
Product:	Container Native Virtualization (CNV)	Reporter:	Ram Lavi <ralavi>
Component:	Networking	Assignee:	Ram Lavi <ralavi>
Status:	ON_QA ---	QA Contact:	Yossi Segev <ysegev>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.13.0	CC:	phoracek
Target Milestone:	---
Target Release:	4.14.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	v4.14.0.rhel9-1146	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ram Lavi 2023-02-16 11:26:29 UTC

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:

Comment 1 Ram Lavi 2023-02-16 11:30:07 UTC

https://github.com/kiagnose/kubevirt-dpdk-checkup/pull/64