Bug 2170437 - kubevirt-dpdk-checkup affinity not set to prefer the objects to run on different nodes
Summary: kubevirt-dpdk-checkup affinity not set to prefer the objects to run on differ...
Keywords:
Status: ON_QA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Networking
Version: 4.13.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: 4.14.0
Assignee: Ram Lavi
QA Contact: Yossi Segev
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-16 11:26 UTC by Ram Lavi
Modified: 2023-07-26 08:10 UTC (History)
1 user (show)

Fixed In Version: v4.14.0.rhel9-1146
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kiagnose kubevirt-dpdk-checkup pull 64 0 None Merged Add Node Affinity and Anti-Affinity logic 2023-07-24 11:03:31 UTC
Red Hat Issue Tracker CNV-25650 0 None None None 2023-02-16 11:31:18 UTC
Red Hat Issue Tracker CNV-26374 0 None None None 2023-03-09 10:16:58 UTC

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:


Note You need to log in before you can comment on or make changes to this bug.