kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update trouble shooting for flannel and vagrant 

Add trouble shooting for kubeadm with flannel pod network in vagrant
This commit is contained in:
Yo-An Lin 2018-01-08 07:21:40 +08:00 committed by GitHub
parent 83dc3c58b1
commit 14a349c249
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/setup/independent/troubleshooting-kubeadm.md
View File

@ -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.