search

luxas / kubeadm-workshop

Showcasing a bare-metal multi-platform kubeadm setup with persistent storage and monitoring
MIT License
679 stars 190 forks source link

DNS won't resolve #24

Closed mitchhh22 closed 7 years ago

mitchhh22 commented 7 years ago

I'm running into an issue with DNS no matter which OS...

Everything create's fine:

root@mitchell-desktop:/etc/default# kubectl get po --all-namespaces
NAMESPACE     NAME                                       READY     STATUS    RESTARTS   AGE
default       nginx-416304662-rfjt3                      1/1       Running   0          18m
kube-system   etcd-mitchell-desktop                      1/1       Running   0          28m
kube-system   kube-apiserver-mitchell-desktop            1/1       Running   0          28m
kube-system   kube-controller-manager-mitchell-desktop   1/1       Running   0          29m
kube-system   kube-dns-2459497834-h88gc                  3/3       Running   0          29m
kube-system   kube-proxy-p88j4                           1/1       Running   0          27m
kube-system   kube-scheduler-mitchell-desktop            1/1       Running   0          28m
kube-system   weave-net-k6dlb                            2/2       Running   0          27m

But trying to resolve anything within a pod does not:

root@mitchell-desktop:/etc/default# kubectl exec -it nginx-416304662-rfjt3 sh
/ # curl google.com
curl: (6) Couldn't resolve host 'google.com'

I noticed dnsmasq is throwing an error:

root@mitchell-desktop:/etc/default# kubectl logs -n kube-system kube-dns-2459497834-h88gc dnsmasq | head -n 20
I0812 16:59:18.348899       1 main.go:76] opts: {{/usr/sbin/dnsmasq [-k --cache-size=1000 --log-facility=- --server=/
cluster.local/127.0.0.1#10053 --server=/in-addr.arpa/127.0.0.1#10053 --server=/ip6.arpa/127.0.0.1#10053] true} /etc/k
8s/dns/dnsmasq-nanny 10000000000}
I0812 16:59:18.349359       1 nanny.go:86] Starting dnsmasq [-k --cache-size=1000 --log-facility=- --server=/cluster.
local/127.0.0.1#10053 --server=/in-addr.arpa/127.0.0.1#10053 --server=/ip6.arpa/127.0.0.1#10053]
I0812 16:59:18.767589       1 nanny.go:111]
W0812 16:59:18.767658       1 nanny.go:112] Got EOF from stdout
I0812 16:59:18.767878       1 nanny.go:108] dnsmasq[13]: started, version 2.76 cachesize 1000
I0812 16:59:18.768167       1 nanny.go:108] dnsmasq[13]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN
 DHCP DHCPv6 no-Lua TFTP no-conntrack ipset auth no-DNSSEC loop-detect inotify
I0812 16:59:18.768291       1 nanny.go:108] dnsmasq[13]: using nameserver 127.0.0.1#10053 for domain ip6.arpa
I0812 16:59:18.768406       1 nanny.go:108] dnsmasq[13]: using nameserver 127.0.0.1#10053 for domain in-addr.arpa
I0812 16:59:18.768497       1 nanny.go:108] dnsmasq[13]: using nameserver 127.0.0.1#10053 for domain cluster.local
I0812 16:59:18.770129       1 nanny.go:108] dnsmasq[13]: reading /etc/resolv.conf
I0812 16:59:18.770341       1 nanny.go:108] dnsmasq[13]: using nameserver 127.0.0.1#10053 for domain ip6.arpa
I0812 16:59:18.770443       1 nanny.go:108] dnsmasq[13]: using nameserver 127.0.0.1#10053 for domain in-addr.arpa
I0812 16:59:18.770527       1 nanny.go:108] dnsmasq[13]: using nameserver 127.0.0.1#10053 for domain cluster.local
I0812 16:59:18.770647       1 nanny.go:108] dnsmasq[13]: using nameserver 127.0.1.1#53
I0812 16:59:18.770742       1 nanny.go:108] dnsmasq[13]: read /etc/hosts - 7 addresses
I0812 17:06:07.325776       1 nanny.go:108] dnsmasq[13]: Maximum number of concurrent DNS queries reached (max: 150)
I0812 17:06:16.195046       1 nanny.go:108] dnsmasq[13]: Maximum number of concurrent DNS queries reached (max: 150)
I0812 17:06:26.221765       1 nanny.go:108] dnsmasq[13]: Maximum number of concurrent DNS queries reached (max: 150)

I followed the workshop to a T on a clean install and no matter which OS (raspbian, hypriot, ubuntu) I get the same result.

Any idea what the issue might be?