{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/33618","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/33618/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/33618/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/33618/events","html_url":"https://github.com/kubernetes/kubernetes/issues/33618","id":179642890,"number":33618,"title":"Issue when using kubeadm with multiple network interfaces","user":{"login":"hgfischer","id":120860,"avatar_url":"https://avatars.githubusercontent.com/u/120860?v=3","gravatar_id":"","url":"https://api.github.com/users/hgfischer","html_url":"https://github.com/hgfischer","followers_url":"https://api.github.com/users/hgfischer/followers","following_url":"https://api.github.com/users/hgfischer/following{/other_user}","gists_url":"https://api.github.com/users/hgfischer/gists{/gist_id}","starred_url":"https://api.github.com/users/hgfischer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hgfischer/subscriptions","organizations_url":"https://api.github.com/users/hgfischer/orgs","repos_url":"https://api.github.com/users/hgfischer/repos","events_url":"https://api.github.com/users/hgfischer/events{/privacy}","received_events_url":"https://api.github.com/users/hgfischer/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/component/kubeadm","name":"component/kubeadm","color":"0052cc"},{"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/team/cluster","name":"team/cluster","color":"d2b48c"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":29,"created_at":"2016-09-27T23:30:57Z","updated_at":"2016-09-29T22:11:07Z","closed_at":"2016-09-28T21:25:12Z","body":"**Is this a request for help?** (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No\r\n\r\n\r\n**What keywords did you search in Kubernetes issues before filing this one?** (If you have found any duplicates, you should instead reply there.): fialed \r\n\r\n---\r\n\r\n**Is this a BUG REPORT or FEATURE REQUEST?** (choose one): BUG REPORT\r\n\r\n**Kubernetes version** (use `kubectl version`): Client Version: version.Info{Major:\"1\", Minor:\"4\", GitVersion:\"v1.4.0\", GitCommit:\"a16c0a7f71a6f93c7e0f222d961f4675cd97a46b\", GitTreeState:\"clean\", BuildDate:\"2016-09-26T18:16:57Z\", GoVersion:\"go1.6.3\", Compiler:\"gc\", Platform:\"linux/amd64\"}\r\n\r\n**Environment**:\r\n- **Cloud provider or hardware configuration**: local VirtualBox machines managed with Vagrant\r\n- **OS** (e.g. from /etc/os-release): Ubuntu 16.04 (both host and VMs)\r\n- **Kernel** (e.g. `uname -a`): Linux kubenode01 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux\r\n- **Install tools**: kubeadm\r\n- **Others**: Vagrant\r\n\r\n\r\n**What happened**: I'm testing a Kubernetes cluster with VirtualBox and Vagrant. Every VM has an NATed interface (eth0) and a Host-Only interface (eth1). I wanted to make the first node try to join the master using the Host-Only IP address because Kubernetes is listening on all interfaces by default.\r\n\r\n\r\n**What you expected to happen**: Since the master is listening to all interfaces available, I was expecting it to just work.\r\n\r\n\r\n**How to reproduce it** (as minimally and precisely as possible): Setup two VMs, with one NATed interface, and one Host-Only interface. Follow steps from http://kubernetes.io/docs/getting-started-guides/kubeadm/ but instead of using exactly the `kubeadm join ...` command-line returned by the master, change the IP address to the one of the Host-Only interface.\r\n\r\n\r\n**Anything else do we need to know**: You can use this to reproduce the issue: https://github.com/hgfischer/Kubernetes14\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/250605885","html_url":"https://github.com/kubernetes/kubernetes/issues/33618#issuecomment-250605885","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/33618","id":250605885,"user":{"login":"hgfischer","id":120860,"avatar_url":"https://avatars.githubusercontent.com/u/120860?v=3","gravatar_id":"","url":"https://api.github.com/users/hgfischer","html_url":"https://github.com/hgfischer","followers_url":"https://api.github.com/users/hgfischer/followers","following_url":"https://api.github.com/users/hgfischer/following{/other_user}","gists_url":"https://api.github.com/users/hgfischer/gists{/gist_id}","starred_url":"https://api.github.com/users/hgfischer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hgfischer/subscriptions","organizations_url":"https://api.github.com/users/hgfischer/orgs","repos_url":"https://api.github.com/users/hgfischer/repos","events_url":"https://api.github.com/users/hgfischer/events{/privacy}","received_events_url":"https://api.github.com/users/hgfischer/received_events","type":"User","site_admin":false},"created_at":"2016-09-29T22:11:07Z","updated_at":"2016-09-29T22:11:07Z","body":"Ok. So I've added both the `--api-advertise-addresses` flag, and the `--hostname-override` flag to `/etc/systemd/system/kubelet.service.d/09-hostname-override.conf`.\r\n\r\nNow, the master starts fine, but when I bootstrap a new node, the new wave-net sublet doesn't starts properly. It ends in a CrashLoopBackOff status. This is what I suppose is the issue, but I could not find how to fix it yet.\r\n\r\n```\r\nSep 29 22:02:58 ubuntu kubelet[9590]: I0929 22:02:58.777738    9590 summary.go:352] Missing default interface \"eth0\" for node:knode01\r\nSep 29 22:02:58 ubuntu kubelet[9590]: I0929 22:02:58.778080    9590 summary.go:352] Missing default interface \"eth0\" for pod:kube-system_weave-net-68oww\r\nSep 29 22:02:58 ubuntu kubelet[9590]: I0929 22:02:58.778267    9590 summary.go:352] Missing default interface \"eth0\" for pod:kube-system_kube-proxy-amd64-qx0wd\r\n```\r\n\r\nI've looked into kubelet cmd-line flags and I could not find something to set the interface name. Also the network binding related flags are defaulting to 0.0.0.0. Do you guys know how to handle this?"}}
{"actor":{"display_login":"hgfischer"}}