Problem
Kubernetes Addons - weave second/slaves pods are not starting up after executing kubeadm join command in the slave machines. weave pods status is CrashLoopBackOff
Cause
Enhanced network feature to use ethernet network interface (eth0) is not configured. "ifconfig -a" shown the result with "ens5" for the private ip network instead of eth0.
Fix
Provision the aws instances with
...
"High" network interface configuration (eth0 should be shown in Aws console network interface). Kubernetes cni (weave) network will use the ethernet to start the cluster(Result: slave node status will be "Ready").
...
Reference aws link: