Kubemark Test-How to point to Master cluster

[K7king]

/kind flake
/area test
/sig scheduling
/sig testing
/kind question
Is this a BUG REPORT or FEATURE REQUEST?:

/kind question

What happened:
I deployed a cluster on AWS. I want to run Kubemark test . By pre-existing they state to give configurations like this
CLOUD_PROVIDER="pre-existing"
KUBEMARK_IMAGE_MAKE_TARGET="push"
CONTAINER_REGISTRY=docker.io
PROJECT="rthallisey"
MASTER_IP="192.168.121.29:6443"

Here what is the Master IP pointing to ?

What you expected to happen:
I want Kubemark test to be performed on the same cluster deployed on AWS.

Environment: AWS

[Kevin-fqh]

I also confuse this。。。I do it in local VM，but the README does not give the details how to use pre-existing。

I think the MASTER_IP is the kubemark master ip, but when I call the start-kubemark.sh, it failed....

my step is described in the end of 44394

[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.

[cy-zheng]

Same issue... I think the document about kubemark pre-existing cluster deployment should be refined.