The cluster have been runned under flannel v0.6.2 , when the container linux update to version 1353. the flanneld update automated. now some app abnormal.
Your Environment
Flannel version: 0.7.0
Backend used (e.g. vxlan or udp): vxlan
Etcd version: 2.3.7
Kubernetes version (if used): 1.5.7
Operating System and version: container linux 1353.7.0
Flannel doesn't assign IP addresses to pods. Maybe you have a problem with host-local IPAM plugin - in which case you should raise it in the containernetworking repo.
Expected Behavior
when I use
kubectl get pods --all-namespace -o wide
, find some duplicate ip for some podsCurrent Behavior
the flanneld start service :
Steps to Reproduce (for bugs)
The cluster have been runned under flannel v0.6.2 , when the container linux update to version 1353. the flanneld update automated. now some app abnormal.
Your Environment