Looks quite interesting for small setups, curious to read more about the limitations (E.g. "Added sqlite3 as the default storage mechanism. etcd3 is still available, but not the default." - what availability promises can this make?)
https://www.sqlite.org/famous.html
I think the "high availability by redundancy" story is oversold.
More generally, an awful lot of systems that'd be fine with a SQL mirror (non-failover), some real backups on top, and a restore-from-backup event every 3-5 years, plus the occasional 1hr maintenance window, are instead made "HA" and "redundant" at 10+x the ops cost and, unless very well done, with even more down-time anyway because they're so damn complex.
https://godoc.org/github.com/etcd-io/etcd/embed
This is something the Kubernetes community might consider as well.