netperf documentation

[extravio]

What would you like to be added:
Can we add a "Get started" section to the README on the netperf tool to describe how to set up the components?

Why is this needed:
I get the following error in the orchestrator's logs:

flag provided but not defined: -testFrom

and the pod doesn't start

[Avnshrai]

flag provided but not defined: -testFrom
how to fix this issue? I am also facing same issue

[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

[k8s-triage-robot]

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[k8s-triage-robot]

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

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

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[bernardgut]

@extravio @Avnshrai did any of you ever figure this out ?

[justin0u0]

The default image hasn't been updated for a while. You can build the image manually and set the image tag on launch with the following steps:

docker build . -t netperf:latest --build-arg GOLANG_VERSION=1.22-bullseye
go run launch.go -image netperf:latest

[AlexanderDotH]

Thanks for posting a resolution. I just built the image and ran the launch command. Somehow my pods are Pending but nothing happens.

[justin0u0]

Thanks for posting a resolution. I just built the image and ran the launch command. Somehow my pods are Pending but nothing happens.

Hi @AlexanderDotH,

A "Pending" status generally indicates that the pod is unable to be scheduled onto a node. You can describe the pod to get more information. Typically this is not related to the application itself.

For more details, you can refer to https://kubernetes.io/docs/tasks/debug/debug-application/debug-pods/#my-pod-stays-pending.

Hope this helps!

[extravio]

@bernardgut @Avnshrai
I managed to make it work thanks to this:
https://www.linkedin.com/pulse/testing-network-performance-iperf3-kubernetes-ghassan-malke-/