Geek Answers Handbook

Skip L3 and route not found for flannel

So, I have a Kubernetes cluster, and I'm using Flannel for the overlay network. It works fine (almost a year actually), then I changed the service to have 2 ports, and suddenly I realized that this is a completely different service that worked previously, and I did not edit:

<Timestamp> <host> flanneld[873]: I0407 18:36:51.705743 00873 vxlan.go:345] L3 miss: <Service IP>
<Timestamp> <host> flanneld[873]: I0407 18:36:51.705865 00873 vxlan.go:349] Route for <Service IP> not found

Is there a common reason for this? I use Kubernetes 1.0.X and Flannel 0.5.5, and I should mention that only one node has this problem, the rest of the nodes are fine. Bad node kube-proxy also says that it cannot find the endpoint of the service.

+4
source share
1 answer

- ... , IP MTU cat /run/flannel/subnet.env ps aux | grep docker ( cat /etc/default/docker)... docker .

sudo ip link set dev docker0 down
sudo brctl delbr docker0

, .
: (.. /run/flannel/subnet.env, /etc/default/docker)

source /run/flannel/subnet.env

echo DOCKER_OPTS=\"-H tcp://127.0.0.1:4243 -H unix:///var/run/docker.sock --bip=${FLANNEL_SUBNET} --mtu=${FLANNEL_MTU}\" > /etc/default/docker

, docker

sudo service docker restart
+4

More articles:


All Articles