Kubernetes 1.9 - DNS CrashLoopBackOff

[jcperezamin]

NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE
kube-system etcd-master 1/1 Running 3 17h 192.168.1.10 master
kube-system kube-apiserver-master 1/1 Running 3 17h 192.168.1.10 master
kube-system kube-controller-manager-master 1/1 Running 3 17h 192.168.1.10 master
kube-system kube-dns-6f4fd4bdf-6mksz 3/3 Running 128 10h 10.32.0.18 node2
kube-system kube-proxy-2q827 1/1 Running 3 17h 192.168.1.13 node3
kube-system kube-proxy-jjd2v 1/1 Running 3 17h 192.168.1.10 master
kube-system kube-proxy-l9876 1/1 Running 3 17h 192.168.1.12 node2
kube-system kube-proxy-rnw92 1/1 Running 3 17h 192.168.1.11 node1
kube-system kube-scheduler-master 1/1 Running 3 17h 192.168.1.10 master
kube-system kubernetes-dashboard-7b7b5cd79b-6fxp2 1/1 Running 0 2h 10.44.0.8 node1
kube-system weave-cortex-agent-5f95d6fd7c-7vsnx 1/1 Running 0 2h 10.44.0.14 node1
kube-system weave-cortex-agent-5f95d6fd7c-vsq6w 1/1 Terminating 0 5h 10.40.0.7 node3
kube-system weave-cortex-agent-5f95d6fd7c-x4mfd 1/1 Terminating 0 10h 10.40.0.13 node3
kube-system weave-cortex-agent-5f95d6fd7c-z65zm 1/1 Terminating 0 8h 10.44.0.14 node1

Kubernetes Version 1.9
Weave Version Latest (from kubernetes website)

What you expected to happen?

What happened?

How to reproduce it?

Anything else we need to know?

Versions:

$ weave version
$ docker version
$ uname -a
$ kubectl version

Logs:

$ docker logs weave

or, if using Kubernetes:

$ kubectl logs -n kube-system <weave-net-pod> weave

Network:

$ ip route
$ ip -4 -o addr
$ sudo iptables-save

[brb]

I don't see any weave-net pod among listed ones. How did you start weave?

[brb]

Closing due to inactivity.