summaryrefslogtreecommitdiff
path: root/development.md
diff options
context:
space:
mode:
authork8s-merge-robot <k8s.production.user@gmail.com>2016-02-01 10:43:52 -0800
committerk8s-merge-robot <k8s.production.user@gmail.com>2016-02-01 10:43:52 -0800
commitf471e1c4d3ad76b942e23f9e4cd3adc2686e9d9b (patch)
treedc3f3836262036b2d63743063f2b7053e483c249 /development.md
parentf4e276aaad176f57e398504b2aec9b1965407057 (diff)
parentf9eba89426a0343fede5ce66134227372c1db371 (diff)
Merge pull request #20366 from pmorie/local-cluster-docs
Auto commit by PR queue bot
Diffstat (limited to 'development.md')
-rw-r--r--development.md30
1 files changed, 29 insertions, 1 deletions
diff --git a/development.md b/development.md
index 06aa870a..608482f7 100644
--- a/development.md
+++ b/development.md
@@ -46,7 +46,7 @@ branch, but release branches of Kubernetes should not change.
## Releases and Official Builds
-Official releases are built in Docker containers. Details are [here](http://releases.k8s.io/HEAD/build/README.md). You can do simple builds and development with just a local Docker installation. If want to build go locally outside of docker, please continue below.
+Official releases are built in Docker containers. Details are [here](http://releases.k8s.io/HEAD/build/README.md). You can do simple builds and development with just a local Docker installation. If you want to build go code locally outside of docker, please continue below.
## Go development environment
@@ -358,6 +358,34 @@ go run hack/e2e.go -v -ctl='get events'
go run hack/e2e.go -v -ctl='delete pod foobar'
```
+## Local clusters
+
+It can be much faster to iterate on a local cluster instead of a cloud-based one. To start a local cluster, you can run:
+
+```sh
+# The PATH construction is needed because PATH is one of the special-cased
+# environment variables not passed by sudo -E
+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.
+
+### E2E tests against local clusters
+
+In order to run an E2E test against a locally running cluster, use the `e2e.test` binary built by `hack/build-go.sh`
+directly:
+
+```sh
+export KUBECONFIG=/path/to/kubeconfig
+e2e.test --host=http://127.0.0.1:8080
+```
+
+To control the tests that are run:
+
+```sh
+e2e.test --host=http://127.0.0.1:8080 --ginkgo.focus="Secrets"
+```
+
## Conformance testing
End-to-end testing, as described above, is for [development