Merge pull request #6870 from c9s/patch-1

Update trouble shooting for flannel and vagrant
2018-01-09 13:30:38 +08:00
parent 0812f2a783 d8d574fa26
commit 2a4a2f9a10
1 changed files with 14 additions and 0 deletions
@@ -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 might indicate 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.