Hi folks, etcd maintains two stable branches [1], at the moment these appear to be the v3.4 and v3.5 series. etcd does not support skip-version updates without dataloss[2] out of the box, operators are encouraged to do online updates. I took a quick sample of some etcd versions: * devstack currently uses etcd v3.3.12 (at time of writing) [3] * kolla uses etcd v3.3.27 [4] * tripleo uses rdo etcd: it appears they're already on 3.4.14 [5] * upstream etcd is at 3.4.27 and 3.5.9 [6] Now, the bad news: The client side endpoints of etcd is changing from `v3alpha` to `v3`, with a `v3beta` step added to ensure maximum confusion [7] tooz, for example, currently defaults to `v3alpha` for the recommended etcd3gw backend [8], but it's configurable in the client side by passing an extra option to the backend url. So just updating etcd from 3.3 to 3.4 usually breaks things until a couple of orchestration updates are made. It seems providing a smooth upgrade path would require coordination between orchestration, services that depend on etcd as a backend, and a couple of middleware libraries. The lack of a skip-version upgrade support means it's probably also better to do this sooner rather than later. 3.4 is already late in its release cycle and due to go out of maintenance soon. Options: * upgrade to 3.4 and use `v3` endpoint everywhere - fix forward? * try to detect endpoints in middleware (etcd3gw) somehow? * ask ChatGPT how to farm goats Links (not permalinks!): [1]: https://github.com/etcd-io/etcd/blob/main/Documentation/contributor-guide/br... [2]: https://etcd.io/docs/v3.3/upgrades/upgrade_3_4/ [3]: https://opendev.org/openstack/devstack/src/branch/master/stackrc#L723 [4]: https://opendev.org/openstack/kolla/src/branch/master/docker/etcd/Dockerfile... [5]: https://review.rdoproject.org/r/plugins/gitiles/rdoinfo/+/master/buildsys-ta... [6]: https://github.com/etcd-io/etcd/releases/ [7]: https://etcd.io/docs/v3.5/dev-guide/api_grpc_gateway/ [8]: https://opendev.org/openstack/tooz/src/branch/master/tooz/drivers/etcd3gw.py...