Kubeadm with remote nodes and master

[mcmw...@gmail.com]

I'm trying to set up a kubernetes cluster on Raspbian raspberry pis. The pis will all be remote, in different locations each, with the master being an Ubuntu EC2 instance with a security group that allows inbound traffic.

I'm trying to use Weave as the CNI but it keeps restarting on the Raspbian node over and over again with the following errors:
Back-off restarting failed container
Liveness probe failed: Get http://127.0.0.1:6784/status: dial tcp 127.0.0.1:6784: connect: connection refused
Or from the docker instance:
ERROR: logging before flag.Parse: E0702 15:35:14.998203 5452 reflector.go:205] github.com/weaveworks/weave/prog/weave-npc/main.go:230: Failed to list *v1.NetworkPolicy: Get https://10.96.0.1:443/apis/networking.k8s.io/v1/networkpolicies?resourceVersion=0: dial tcp 10.96.0.1:443: i/o timeout

That IP is the virtual IP for my master, not the public exposed IP I use.

Communication seems to work, but the weave container just keeps restarting over and over again.

I've been hanging my head against the wall for a week now and can't get anywhere, any one else tried this solution? Am I way out of my league trying to create a kubernetes cluster like this?

Any help is appreciated.

[mcmw...@gmail.com]

Found my solution here: https://gist.github.com/squidpickles/dda268d9a444c600418da5e1641239af

Seems the cluster needs to support both amd65 and arm versions of kube-proxy