[WIP] Kube-batch perf test

[shivramsrivastava]

What this PR does / why we need it:
This PR adds the scheduler_perf test to kube-batch, this is similar to the scheduler_perf test found in the k8s project for the default scheduler.

Special notes for your reviewer:

1. This are the initial changes.

TODO:

• Adding the test framework api-server with CRD support.
• Adding Pod-Affinity/Anti-Affinity and the Node-Affinity/Anti-Affinity tests.
• Updating the README
• Running the test and generate sample graphs
• Added the initial code and updated vendor.
• Added methods to run kube-batch from within the perf test.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: shivramsrivastava
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: k82cn

If they are not already assigned, you can assign the PR to them by writing /assign @k82cn in a comment when ready.

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

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

[shivramsrivastava]

/assign @k82cn

[k82cn]

why do we copy code here? we should also use import for those package.

[liggitt]

/unassign

[k82cn]

/uncc @liggitt @deads2k

[k82cn]

@shivramsrivastava , are you still working on this?

[shivramsrivastava]

I am putting an hold on this task for now, since i am unable to resolve the api-server issue for crd support.
I will take up others issues in the meantime.
If you have any suggestions on which issue to take let me know, please?

[shivramsrivastava]

/hold

[k82cn]

@TommyLike , @hzxuzhonghu , would you help to review this PR and get it done ASAP? we're testing the performance of kube-batch, and this is important for us.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.