summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorThibault Serot <thibserot@gmail.com>2015-12-30 23:48:00 +0100
committerThibault Serot <thibserot@gmail.com>2016-01-30 19:45:59 +0100
commita4a50507a11f6f407c554bc8f4f19bc0a268a32a (patch)
treeaf1e122fcb425119972cb4ede30a870b877146be
parent3679b53fda8d9f29447a4f93549a83427311877b (diff)
Enabling DNS support in local-up-cluster.sh
-rw-r--r--running-locally.md11
1 files changed, 10 insertions, 1 deletions
diff --git a/running-locally.md b/running-locally.md
index 257b2522..dc9120fd 100644
--- a/running-locally.md
+++ b/running-locally.md
@@ -166,7 +166,16 @@ One or more of the Kubernetes daemons might've crashed. Tail the logs of each in
#### The pods fail to connect to the services by host names
-The local-up-cluster.sh script doesn't start a DNS service. Similar situation can be found [here](http://issue.k8s.io/6667). You can start a manually. Related documents can be found [here](../../cluster/addons/dns/#how-do-i-configure-it)
+To start the DNS service, you need to set the following variables:
+
+```sh
+KUBE_ENABLE_CLUSTER_DNS=true
+KUBE_DNS_SERVER_IP="10.0.0.10"
+KUBE_DNS_DOMAIN="cluster.local"
+KUBE_DNS_REPLICAS=1
+```
+
+To know more on DNS service you can look [here](http://issue.k8s.io/6667). Related documents can be found [here](../../cluster/addons/dns/#how-do-i-configure-it)