Consider other data-path test tools

[jtaleric]

What would you like to be added:
Consider adding (not suggesting we replace) https://github.com/cloud-bulldozer/k8s-netperf

This is a similar tool to what you have today. However this tools uses netperf (or iperf3), and tests stream,rr and crr. This tool also collects UDP loss and TCP re-transmissions. If Prometheus is available, k8s-netperf will scrape specific metrics (node and pod utilization) and report to the user.

Why is this needed:
Not needed, but could be a interesting addition for data-path testing.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[jtaleric]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[jtaleric]

/remove-lifecycle stale