Fix e2e network performance test

[aojea]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:

/kind api-change

/kind bug

/kind cleanup
/kind deprecation
/kind design
/kind documentation

/kind failing-test

/kind feature
/kind flake

What this PR does / why we need it:

The agnhost image has the agnhost binary as entrypoint.
The networking performance test need to run iperf overriding the entrypoint

Which issue(s) this PR fixes:

Fixes #90450

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[aojea]

/assign @thockin @dcbw
/sig network
/priority important-soon

[aojea]

I've tested it locally, don't know if this is running in some CI

bazel-bin/test/e2e/e2e.test -ginkgo.focus="Feature:Networking-Performance" -num-nodes 2
....
Apr 25 16:42:24.881: INFO: Selector matched 1 pods for map[app:iperf-e2e-cli-pod]
Apr 25 16:42:24.881: INFO: ForEach: Found 1 pods from the filter.  Now looping through them.
Apr 25 16:42:24.881: INFO: Running '/usr/local/bin/kubectl --server=https://127.0.0.1:35859 --kubeconfig=/home/aojeagarcia/.kube/config logs iperf-e2e-cli-pod-0 iperf-client --namespace=network-perf-7184'
Apr 25 16:42:24.999: INFO: stderr: ""
Apr 25 16:42:24.999: INFO: stdout: "20200425144219,10.244.1.7,55390,10.103.237.250,8002,3,0.0-10.0,41231187968,32984805241\n"
Apr 25 16:42:24.999: INFO: 20200425144219,10.244.1.7,55390,10.103.237.250,8002,3,0.0-10.0,41231187968,32984805241
....
Ran 2 of 5009 Specs in 50.958 seconds
SUCCESS! -- 2 Passed | 0 Failed | 0 Pending | 5007 Skipped

[SataQiu]

/lgtm

[aojea]

/retest

[aojea]

/assign @danwinship
do you mind take a look for approval?
it's a simple fix, the agnhost image has a binary as entrypoint, so we need to override it with a shell to be able to execute iperf inside.
I've tested the change locally

[aojea]

/retest

[cmluciano]

@aojea I don't have approver power but will try this out locally and give another review. Can you confirm how you ran this test locally? I'm gonna try a kubetest build against a cloud cluster.

[aojea]

@aojea I don't have approver power but will try this out locally and give another review. Can you confirm how you ran this test locally? I'm gonna try a kubetest build against a cloud cluster.

I test it using kind kubernetes-sigs/kind#1181 (comment)

[danwinship]

I've tested it locally, don't know if this is running in some CI

It probably runs in one of the periodic jobs, not something you can run from a PR. One way to get around that is to just push a temporary commit changing the tags on the test you want to run so it's no longer skipped in the default runs. But anyway, the fix looks right and you tested it.

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aojea, danwinship

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• test/e2e/network/OWNERS [danwinship]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment