Added benchmark of kube-batch

[k82cn]

DESCRIPTION: -- symptom of the problem a customer would see

After enabled pod affinity/anti-affinity at #418 , we need to know the impact to the kube-batch performance.

[Jeffwan]

1. I think this one depends on Add performance metrics #487? Once kube-batch exposes metric, it would be easy to check benchmark result.
2. Do we also want to add benchmark utilities like https://github.com/kubernetes/perf-tests?

[k82cn]

both are necessary :)

metrics is helpful for product, perf is helpful for test, debug. I think we can do metrics firstly.

[thandayuthapani]

For benchmark of kube-batch using scheduler-perf a WIP PR has been raised #597, but there are problems in scheduler-perf test integration suite, since they bring up API Server without CRD Support, but kube-batch depends on CRDs like PodGroup, We are trying to add CRD Capability to the API Server, which is being brought up by scheduler-perf integration test suite. This is where we are working on now to bring CRD capability to that API Server, and that is our blocking point now.

[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: Closing this issue.

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.