host and internet connectivity in combination with Kubernetes

[slintes]

Hi. I'm evaluating using weave in combination with docker, and have a setup running based on https://github.com/errordeveloper/weave-demos/tree/master/poseidon.
I have to issued with this setup:

1. I can not reach other hosts (e.g. for using etcd running on an other CoreOS instance. Workaround: run another etcd in a docker container)
2. I can not reach "the internet" (usecase: run an own docker registry in a container, which also builds the images itself, based on Dockerfiles hosted on github...)

I discussed this already with Ilya, and he pointed me to kubernetes/kubernetes#15. While on the one hand that sounds somewhat reasonable to me (I'm not an network expert), I only can say that with flannel I have access to other hosts and to the internet...?

[rade]

Hmm. If, as you say, this works with flannel then it should certainly work with weave.

Re your first point, so you want to run etcd on the host and have to talk to other hosts over weave? That should be possible through service routing. Did you try that?

Re your second point... is that a problem with name resolution or routing? Can you reach "the internet" by IP address?

[slintes]

1. I was not aware of service routing yet, thanks, will have look.
2. Both. I can not ping internet servers by name (name is not resolved) or by IP address.

[errordeveloper]

@slintes a few more details would help:

• are you running the same version of kubernetes in your test with flannel and weave?
• do you run docker --iptables=false --ip-masq=false in both of the tests as well?

[slintes]

1. yes, both setups Kubernetes 0.5.4
2. yes, see https://github.com/slintes/CoreOSKubernetesTest/blob/weave/Cluster/coreos-userdata#L120

[slintes]

oh wait, sorry, with flannel I don't use these flags, see https://github.com/slintes/CoreOSKubernetesTest/blob/master/Cluster/coreos-userdata
Can I just skip the flags with weave, too?

[errordeveloper]

Sure, those flags are the reason. I have put them there in the first place as per Kubernetes docs. I suppose you could try to remove them and see how it plays out.

[slintes]

That was easy ;) Works, thanks!

[errordeveloper]

I'd like to keep this open, until I make an update to the blog post...

[errordeveloper]

@slintes could you confirm which revision of Kubernetes you are running?

[errordeveloper]

@slintes please comment on kubernetes/kubernetes#15, so we can clarify the upstream status.

[alwansm]

Hello I am facing the same problem is there any update the previous solution didn't work