Add note about how to run performance test

[alexander-ding]

What type of PR is this?

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

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Adds some basic instruction on how to run performance tests.

Which issue(s) this PR fixes:

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

NONE

/cc @mauriciopoppe
/cc @mattcary

[k8s-ci-robot]

Hi @alexander-ding. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[mattcary]

/ok-to-test
/lgtm
/approve

Thanks!

Out of curiosity, did you try these with kubetest2 at all?

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexander-ding, mattcary

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:

• OWNERS [mattcary]

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

[alexander-ding]

/ok-to-test /lgtm /approve

Thanks!

Out of curiosity, did you try these with kubetest2 at all?

I tried a bit, but I wasn't sure how to port the --ginkgo-args to kubetest2. I think kubetest2 uses a newer version of Ginkgo, and the K8s specific flags like --node-os-distro=windows aren't recognized. There might be another place to pass these though. I just didn't look into it enough.

[mattcary]

I tried a bit, but I wasn't sure how to port the --ginkgo-args to kubetest2. I think kubetest2 uses a newer version of Ginkgo, and the K8s specific flags like --node-os-distro=windows aren't recognized. There might be another place to pass these though. I just didn't look into it enough.

Gotcha, cool. We'll be updating to kubetest2 eventually so I'll add your frictions to our list.