Hi, According to what I am informed, users who are using APISIX 2.x from the APISIX community, have upgraded up to v3. But I cannot touch most of users from the SkyWalking community. This is why I write to dev mail list for getting more information and discussion about this.
Besides this, IMO, we could introduce a new module for etcd v3 because they are from different groups. In other words, v2 and v3 don't make conflict. JunXu Chen <[email protected]> 于2021年6月25日周五 下午2:03写道： > vote for option 2 > > because etcd 3.5 is the last version that supports V2 API. Flags > --enable-v2 and --experimental-enable-v2v3 are now deprecated and will be > removed in etcd v3.6 release. > > On Fri, 25 Jun 2021 at 13:56, wei jin <[email protected]> wrote: > > > I think the 3rd way may be a good choice. > > > > Daming <[email protected]> 于2021年6月25日周五 下午12:41写道： > > > > > Hi, the SkyWalking community, > > > > > > Currently, we have supported the ETCD v2 protocol as an optional plugin > > for > > > a configuration center or service discovery in cluster module. > > > It is a long time ago since ETCD v3 protocol release. More and more > users > > > deployed ETCD v3, so that I would like to introduce ETCD v3 into the > > > community. There are 3 options following. > > > 1. we don't need this. > > > 2. replace etcd v2 by etcd v3. > > > 3. v2 and v3 co-exist. > > > > > > ------------------ > > > Haochao Zhuang(@dmsolr) > > > Apache SkyWalking > > > > > >
