From 14a349c249430302658736ce3cebe3f6dabb00a6 Mon Sep 17 00:00:00 2001 From: Yo-An Lin Date: Mon, 8 Jan 2018 07:21:40 +0800 Subject: [PATCH] Update trouble shooting for flannel and vagrant Add trouble shooting for kubeadm with flannel pod network in vagrant --- docs/setup/independent/troubleshooting-kubeadm.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/setup/independent/troubleshooting-kubeadm.md b/docs/setup/independent/troubleshooting-kubeadm.md index 8655e01eba..905c936154 100644 --- a/docs/setup/independent/troubleshooting-kubeadm.md +++ b/docs/setup/independent/troubleshooting-kubeadm.md @@ -161,3 +161,17 @@ kubectl -n ${NAMESPACE} describe pod ${POD_NAME} kubectl -n ${NAMESPACE} logs ${POD_NAME} -c ${CONTAINER_NAME} ``` + +### Default NIC When using flannel as the pod network in Vagrant + +The following error indicates that something was wrong in the pod network: + +``` +Error from server (NotFound): the server could not find the requested resource +``` + +If you're using flannel as the pod network inside vagrant, then you will have to specify the default interface name for flannel. + +Vagrant typically assigns two interfaces to all VMs. The first, for which all hosts are assigned the IP address 10.0.2.15, is for external traffic that gets NATed. + +This may lead to problems with flannel. By default, flannel selects the first interface on a host. This leads to all hosts thinking they have the same public IP address. To prevent this issue, pass the --iface eth1 flag to flannel so that the second interface is chosen.