diff options
| author | Kubernetes Submit Queue <k8s-merge-robot@users.noreply.github.com> | 2016-10-09 17:46:10 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-10-09 17:46:10 -0700 |
| commit | 83de8a4818207824b3eb4b824235e924ece4734d (patch) | |
| tree | d4a58044b940bfad6949e77b77b3a8b7eb4ab6ab | |
| parent | 7f9358461560ee78d26b6d541e91f71bf4db69dc (diff) | |
| parent | 2c0e8827a110dcff277b45d37b070fc77f8c8a27 (diff) | |
Merge pull request #34239 from gnufied/update-e2e-docs
Automatic merge from submit-queue
Update documentation for running e2e tests locally
**What this PR does / why we need it**:
The docs for running e2e tests locally needs to be updated.
check_node_count option has been removed and developers usually
need to perform additional steps do get it going.
| -rw-r--r-- | e2e-tests.md | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/e2e-tests.md b/e2e-tests.md index 372cc683..417b7207 100644 --- a/e2e-tests.md +++ b/e2e-tests.md @@ -386,6 +386,9 @@ sudo PATH=$PATH hack/local-up-cluster.sh This will start a single-node Kubernetes cluster than runs pods using the local docker daemon. Press Control-C to stop the cluster. +You can generate a valid kubeconfig file by following instructions printed at the +end of aforementioned script. + #### Testing against local clusters In order to run an E2E test against a locally running cluster, point the tests @@ -393,7 +396,9 @@ at a custom host directly: ```sh export KUBECONFIG=/path/to/kubeconfig -go run hack/e2e.go -v --test --check_node_count=false +export KUBE_MASTER_IP="http://127.0.0.1:<PORT>" +export KUBE_MASTER=local +go run hack/e2e.go -v --test ``` To control the tests that are run: |