weave second pod(slave pod) status is CrashLoopBackOff

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

weave second/slaves pods are not starting up after executing kubeadm join command in the slave machines.network interface issue (OR) port conflicts in slave machines. Please check the weave pod log to check the port bind issue. In this case, 6783 port conflicts between slave machine kube weave and gitlab alertmanager.  

Fix

Provision the aws instances with "High" network interface configuration (In Aws console, specific instance configuration network interface should be eth0). Kubernetes cni (weave) network will use the ethernet to start the cluster(Result: slave node status will be "Ready").

(OR)

stopped gitlab. Then, did "kubeadm join" command in slave machine.