Glad you got it working. The version thing is normal since you can use etcdctl with both APIs. It just happens to have a 2.x version.
> On May 30, 2017, at 1:09 AM, Osman Ali <[email protected]> wrote: > > Thanks! This was very useful. Managed to solve for a single instance of etcd > v3 as follows: > > Used etcd-member.service with the following drop in: > > [Service] > Environment="ETCD_ADVERTISE_CLIENT_URLS=http://$INTERNAL_IP:2379"; > Environment="ETCD_LISTEN_CLIENT_URLS=http://0.0.0.0:2379"; > > I manually inputted the internal ip value. > > Then: > > ETCDCTL_API=3 etcdctl set /coreos.com/network/config > '{"Network":"10.40.0.0/16", "Backend": {"Type": "gce"}}' > > Ran with latest version of flannel and was able to acquire the subnet least. > > Next steps will be to setup etcd v3 cluster and add then secure cluster. > > When I run etcdctl -v, I still get: > > etcdctl version 2.3.7 > > Even after I run export ETCDCTL_API=3, the value is the same for the version. > > Does this indicate that I am not using v3 or just the backward compatibility? > > Thanks. > > > > On Monday, May 29, 2017 at 12:03:08 PM UTC-7, Rob Szumski wrote: > Answers below. > >> 1. How do I use etcd v3 on GCE to setup the flannel backend? >> >> Is there any updated documentation? > > Once you have an etcd v3 cluster, you will need to use/export this variable > for etcdctl: ETCDCTL_API=3. The documented command should work fine after > that. > >> >> 2. How do I setup etcd v3 on GCE using a cloud config file? >> >> I have tried to create a an upgraded cluster using a cloud config file as >> follows: > >> 3. How do I manage etcd versions as they are both setup as services? > > Here’s an example template > <https://github.com/coreos/matchbox/blob/master/examples/ignition/etcd3.yaml>. > This uses the “etcd-member” service, which runs etcd as a container with the > flags specified. It allows you to specify the container version as well, to > give you more control over the service. > > Hope that helps. > > - Rob >
