Flannel: About etcd version

[smarkm]

Current Behavior

flannel can not working well with etcd 3

Possible Solution

1. Whether to plan to support etcd 3 as dataStore?
2. If no plan, please make clear for only support etcd 2 now

Your Environment

• Flannel version: 0.5.3+git
• Etcd version: 3.5

[meibin353]

Set the parameter --enable-v2 to true in etcd, etcd supports flannel access.

[zkzhu0110]

Thanks for reminding us of this. Currently, I have also came across this problem.

When I set the network for etcd 3 to connect docker network between hosts as this command,

etcdctl put /coreos.com/network/config '{"Network":"172.16.0.0/12", "Backend":{"Type":"vxlan"}}'

I came across the following problem after input "flanneld":

I1028 17:10:54.868704   79569 main.go:514] Determining IP address of default interface
I1028 17:10:54.869922   79569 main.go:527] Using interface with name enp59s0f0 and address 10.10.2.41
I1028 17:10:54.869942   79569 main.go:544] Defaulting external address to interface address (10.10.2.41)
I1028 17:10:54.870460   79569 main.go:244] Created subnet manager: Etcd Local Manager with Previous Subnet: None
I1028 17:10:54.870487   79569 main.go:247] Installing signal handlers
E1028 17:10:54.872134   79569 main.go:382] Couldn't fetch network config: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint.
timed out
E1028 17:10:55.872961   79569 main.go:382] Couldn't fetch network config: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint.
timed out

[KeepMovingNo1]

@zkzhu0110 I have encountered the problem too.
Couldn't fetch network config: client: response is invalid json. The endpoint is probably not valid etcd cluster endpoint,

How did you solve it,
Version:
Flannel: 0.12
etcd: V3.4.9

[taomaree]

works for etcd 3.4.10:
etcd server: add --enable-v2
etcd client: ETCDCTL_API=2 etcdctl set /coreos.com/network/config '{ "Network": "10.5.0.0/16", "Backend": {"Type": "vxlan"}}'