Installing a Kubernetes pod network for cluster nodes hosted on VirtualBox VMs -

on os x 10.11.6, created 4 centos 7 vms each 2 interfaces ( 1 nat, , 1 host-only network.) in virtualbox. each vm's host-only interface receives ip via dchcp , dns via dnsmasq.

os x running dnsmasq configure via /usr/local/etc/dnsmasq.conf file contains:

interface=vboxnet0  bind-interfaces  dhcp-range=vboxnet0,192.168.56.100,192.168.56.200,255.255.255.0,infinite dhcp-leasefile=/usr/local/etc/dnsmasq.leases  local=/dev/ expand-hosts domain=dev  address=/kube-master.dev/192.168.56.100 address=/kube-minion1.dev/192.168.56.101 address=/kube-minion2.dev/192.168.56.102 address=/kube-minion3.dev/192.168.56.103 address=/vbox-host.dev/192.168.56.1  dhcp-host=08:00:27:09:48:16,192.168.56.100 dhcp-host=0a:00:27:00:00:00,192.168.56.1 dhcp-host=08:00:27:95:ae:39,192.168.56.101 dhcp-host=08:00:27:97:c9:d4,192.168.56.102 dhcp-host=08:00:27:9b:ad:b5,192.168.56.103 

i can ssh each vm through respective host-only adapter's associated address (e.g., kube-master.dev, kube-minion1.dev, kube-minion2.dev, kube-minion3.dev), ,

yum update  

skipping few steps, point of installing kubeadm per http://kubernetes.io/docs/getting-started-guides/kubeadm/, is:

cat <<eof > /etc/yum.repos.d/kubernetes.repo [kubernetes] name=kubernetes baseurl=http://yum.kubernetes.io/repos/kubernetes-el7-x86_64 enabled=1 gpgcheck=1 repo_gpgcheck=1 gpgkey=https://packages.cloud.google.com/yum/doc/yum-key.gpg    https://packages.cloud.google.com/yum/doc/rpm-package-key.gpg eof setenforce 0 yum install -y docker kubelet kubeadm kubectl kubernetes-cni ebtables systemctl enable docker && systemctl start docker systemctl enable kubelet && systemctl start kubelet 

then unclear me if following correct on kube-master.dev execute

kubeadm init --api-advertise-addresses=192.168.56.100 --api-external-dns-names=kube-master.dev 

and on each minion execute:

rm -rf /etc/kubernetes/manifests/ kubeadm join --token=e7cd12.68011e93d5db7670 192.168.56.100 

on kube-master.dev, run

kubectl nodes 

to verify each node has joined cluster.

the command returns:

name               status    age kube-master.dev    ready     44m kube-minion1.dev   ready     40m kube-minion2.dev   ready     39m kube-minion3.dev   ready     39m 

indicating things groovy.

afterward, things go entirely off rail when attempt install pod network.

on kube-master.dev, run:

kubectl apply -f https://git.io/weave-kube 

to install weave net, , once pod network installed start monitoring network working via executing:

watch kubectl pods --all-namespaces 

and

kube-dns-654381707-05i1t                  0/3 

never moves off of zero.

so please doing wrong? i've hammered @ days. kubeadm documentation bit thin in few place, i'm not sure init'ed master correctly, , installing pod network bit conjecture on part. also, haven't found tutorial other kubernetes kubeadm , associated youtube video documenting use of kubeadm set kubernetes cluster.