From 800b98546db81835ffededea3e3478ef529eefa1 Mon Sep 17 00:00:00 2001 From: "Brandon B. Jozsa" Date: Thu, 22 Dec 2016 23:17:55 -0500 Subject: [PATCH] Update getting-started.md --- docs/installation/getting-started.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/docs/installation/getting-started.md b/docs/installation/getting-started.md index 99812bc718..1c60a1f55e 100644 --- a/docs/installation/getting-started.md +++ b/docs/installation/getting-started.md @@ -116,7 +116,7 @@ No events. admin@kubenode01:~$ ``` -As you can see by this example, `10.25.162.193` is the `kube-dns-2924299975-xxtrg` endpoint. Now, have a look at the current `kube-controller-manager-kubenode01` `/etc/resolv.conf`: +As you can see by this example, `10.96.0.10` is the `kube-dns`IP. Now, have a look at the current `kube-controller-manager-kubenode01` `/etc/resolv.conf`: ``` admin@kubenode01:~$ kubectl exec kube-controller-manager-kubenode01 -n kube-system -- cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) @@ -130,9 +130,7 @@ admin@kubenode01:~$ What we need is for `kube-controller-manager-kubenode01` `/etc/resolv.conf` to look like this: ``` admin@kubenode01:~$ kubectl exec kube-controller-manager-kubenode01 -n kube-system -- cat /etc/resolv.conf -# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) -# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN -nameserver 10.25.162.193 +nameserver 10.96.0.10 nameserver 192.168.1.70 nameserver 8.8.8.8 search svc.cluster.local jinkit.com @@ -143,7 +141,7 @@ You can change this by doing the following: ``` admin@kubenode01:~$ kubectl exec kube-controller-manager-kubenode01 -it -n kube-system -- /bin/bash root@kubenode01:/# cat < /etc/resolv.conf -nameserver 10.25.162.193 +nameserver 10.96.0.10 nameserver 192.168.1.70 nameserver 8.8.8.8 search svc.cluster.local jinkit.com