Questions often asked when using etcd v3 on CoreOS Container Linux
The version 3 series is the latest edition of the etcd binary and API. The current release is the latest release in the version 3 series.
Container Linux includes a systemd service, etcd-member.service, that knows how to fetch and run etcd v3 in a Linux container. No etcd v3-series binary is directly included in the Container Linux filesystem.
For reasons of compatibility, previous, deprecated versions of etcd, named etcd and etcd2, are included in the Container Linux filesystem until they complete their sunset schedules and are finally removed.
The etcd (v0) binary will be removed from Container Linux in May, 2017.
The etcd2 binary will be included in the OS until June, 2018.
The recommended way to run etcd on Container Linux is to use the etcd-member service.
Version 3-series etcd binaries are packaged in a Linux container and instantiated by the etcd-member.service systemd unit.
No. The etcd v3 API uses gRPC rather than plain text HTTP. Use etcdctl to interact with the etcd v3 API.
The preferred way to provision any Container Linux machine is with a Container Linux Config. See an example Container Linux Config for etcd in the getting started with etcd guide.
The preferred way to configure a Container Linux machine is with Container Linux configs and Ignition. The Container Linux Config Transpiler docs include an etcd configuration example.