github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-08-10 04:27:54 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #34239 from gnufied/update-e2e-docs

Browse Source 
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.
This commit is contained in:
Kubernetes Submit Queue 2016-10-09 17:46:10 -07:00 committed by GitHub
commit b359034817
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/devel/e2e-tests.md
View File

@ -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 This will start a single-node Kubernetes cluster than runs pods using the local
docker daemon. Press Control-C to stop the cluster. 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 #### Testing against local clusters
In order to run an E2E test against a locally running cluster, point the tests 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 ```sh
export KUBECONFIG=/path/to/kubeconfig 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: To control the tests that are run: