diff options
| author | Hemant Kumar <gethemant@gmail.com> | 2016-10-06 10:51:49 -0400 |
|---|---|---|
| committer | Hemant Kumar <gethemant@gmail.com> | 2016-10-06 10:51:49 -0400 |
| commit | 2c0e8827a110dcff277b45d37b070fc77f8c8a27 (patch) | |
| tree | efa3592841c9343edb05164f43da5f8c39eed6dd | |
| parent | 0bb9abbaaa14df4c5fc1337ace470d88cbc5c8a5 (diff) | |
Update documentation for running e2e tests locally
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 0200afb8..b1aadb81 100644 --- a/e2e-tests.md +++ b/e2e-tests.md @@ -383,6 +383,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 @@ -390,7 +393,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: |