openstack/openstack-helm
Code Issues Proposed changes

Update getting-started.md

Browse Source
This commit is contained in:
Brandon B. Jozsa 2016-12-22 23:17:55 -05:00 committed by GitHub
parent 7d65bcef0b
commit 800b98546d
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/installation/getting-started.md
View File

@ -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 <<EOF > /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