search

cloud-bulldozer / benchmark-operator

The Chuck Norris of cloud benchmarks
Apache License 2.0
282 stars 127 forks source link

iPerf: work-around for ipv6 traffic type on dual-stack cluster #815

Closed elenagerman closed 1 year ago

elenagerman commented 1 year ago

Description

In the case of a dual-stack cluster, when ipv6 traffic is required, and even the '-6' option is provided, the 'iperf3 -c ' command will always use an ipv4 address. The openshift preference in the case of dual-stack is always ipv4. And this is a reason the server pod will always have ipv4 as a main pod address (podIP value).

As a result, when '-6' option is used in this case and 'iperf3 -c ' will run to the ipv4 address, the pod execution fails.

Fixes

switch to the item.status.podIPs list handling instead of item.status.podIP when ipv6 is required

elenagerman commented 1 year ago

possible solution for the https://github.com/cloud-bulldozer/benchmark-operator/issues/814

codecov-commenter commented 1 year ago

Codecov Report

Merging #815 (d5627de) into master (0954437) will increase coverage by 0.30%. The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@            Coverage Diff             @@
##           master     #815      +/-   ##
==========================================
+ Coverage   53.17%   53.47%   +0.30%     
==========================================
  Files           8        8              
  Lines         331      331              
==========================================
+ Hits          176      177       +1     
+ Misses        155      154       -1
Flag Coverage Δ
gha 53.47% <ø> (+0.30%) :arrow_up:
python-3.9 53.47% <ø> (+0.30%) :arrow_up:
unit 53.47% <ø> (+0.30%) :arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

see 1 file with indirect coverage changes