From 4c0f3b84380ee466a835ed5750e419c3d62332f6 Mon Sep 17 00:00:00 2001 From: Hemant Kumar Date: Thu, 6 Oct 2016 10:51:49 -0400 Subject: [PATCH] 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. --- docs/devel/e2e-tests.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/devel/e2e-tests.md b/docs/devel/e2e-tests.md index 0200afb8623..b1aadb811e1 100644 --- a/docs/devel/e2e-tests.md +++ b/docs/devel/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:" +export KUBE_MASTER=local +go run hack/e2e.go -v --test ``` To control the tests that are run: