diff options
| author | k8s-merge-robot <k8s.production.user@gmail.com> | 2016-02-22 23:45:44 -0800 |
|---|---|---|
| committer | k8s-merge-robot <k8s.production.user@gmail.com> | 2016-02-22 23:45:44 -0800 |
| commit | 7d3e4e7636e0d9c4510a9d2d45d1f93c2be8e113 (patch) | |
| tree | fb04da32c18b54e3abe36eb60d22ef8c46c69c96 | |
| parent | 8593ad844065d049d9c954aaabbe340f8e189846 (diff) | |
| parent | 0b50d4589f036abd1dbd67a864bc85acc768d715 (diff) | |
Merge pull request #21644 from thibserot/dns2
Auto commit by PR queue bot
| -rw-r--r-- | running-locally.md | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/running-locally.md b/running-locally.md index e5b1b40d..a84bb08c 100644 --- a/running-locally.md +++ b/running-locally.md @@ -175,9 +175,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) <!-- BEGIN MUNGE: GENERATED_ANALYTICS --> |