You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have kubernetes running locally using hack/local-up-cluster.sh. I then installed the add-ons using: cluster/ubuntu/deployAddons.sh. However, DNS is not working properly as seen by:
$ 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 127.0.1.1
search localdomain
$ kubectl get ep --all-namespaces
NAMESPACE NAME ENDPOINTS
default kubernetes 192.168.245.149:6443
kube-system kube-dns 172.17.0.2:53,172.17.0.2:53
kube-system kube-ui 172.17.0.3:8080
Note: the only change I made to the default configuration was in cluster/ubuntu/config-default.sh. I changed the following lines to make the service ip range compatible with the range listed in local-up-cluster.sh:
I was able to get this working by adding the following to the kubelet startup command within hack/local-up-cluster.sh:
--cluster-dns=10.0.0.10 --cluster-domain=cluster.local
I have kubernetes running locally using hack/local-up-cluster.sh. I then installed the add-ons using: cluster/ubuntu/deployAddons.sh. However, DNS is not working properly as seen by:
Running nslookup within a simple buxybox pod:
Here are the skydns logs:
resolv.conf on the skydns pod
$ kubectl --namespace=kube-system exec kube-dns-v9-k9awk -c skydns -- cat /etc/resolv.conf search localdomain nameserver 127.0.1.1 options ndots:5
resolv.conf on the host
The skydns pod is not running with net=host
The command line args for theskydns process.
# command = "/skydns" - -machines=http://127.0.0.1:4001 - -addr=0.0.0.0:53 - -ns-rotate=false - -domain=cluster.local.
Endpoints
Note: the only change I made to the default configuration was in cluster/ubuntu/config-default.sh. I changed the following lines to make the service ip range compatible with the range listed in local-up-cluster.sh:
Any help you can provide would be greatly appreciated.
The text was updated successfully, but these errors were encountered: