New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start ubuntu cluster in vagrant cannot customise flannel default interface in config-default.sh. #17788

Closed
tongda opened this Issue Nov 25, 2015 · 6 comments

Comments

Projects
None yet
4 participants
@tongda

tongda commented Nov 25, 2015

When running k8s cluster in vagrant and bootstrap it using cluster/ubuntu scripts, I found that pods cannot access each other using flannel ip. After digging into this problem, I found that it is because flannel would look for default interface after start up. Since the default interface (eth0, ip is 10.0.2.15 in my case) is a nat interface in vagrant VM, flannel will use 10.0.2.15 as external interface. However, the correct binding should be eth1, which is the hostonly network interface, so that I have to modify the /etc/default/flanneld like this:

FLANNEL_OPTS="-iface=eth1 --etcd-endpoints=http://172.28.128.12:4001"

I think the -iface option should be configurable in config-default.sh.

@dalanlan

This comment has been minimized.

Contributor

dalanlan commented Nov 26, 2015

Agreed. I think @MikeSpreitzer has a pr ongoing.
If he's not available for this (cla thing), i'll pick it up.

@MikeSpreitzer

This comment has been minimized.

Member

MikeSpreitzer commented Nov 26, 2015

I have a fix but my company has not done the CLA yet. That is in progress, but I do not know when it will complete. Until then I can not contribute a PR.

@MikeSpreitzer

This comment has been minimized.

Member

MikeSpreitzer commented Nov 26, 2015

It is not a difficult fix. We are talking about issue #17013.

@tongda

This comment has been minimized.

tongda commented Nov 27, 2015

I was planning to fix this myself. Since @MikeSpreitzer is working, I will wait for it. ;)

@MikeSpreitzer

This comment has been minimized.

Member

MikeSpreitzer commented Nov 27, 2015

@tongda No, do not wait for me, I do not know when my company will sign the CLA.
But do see issue #17013.

@dalanlan

This comment has been minimized.

Contributor

dalanlan commented Nov 27, 2015

Feel free to fix it then:)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment