Piotr Tabor

I would think about a longer term perspective for the 'etcdutl' tool. I think we should eventually get rid of `etcd-dump-logs` and `etcd-dump-db` tools and position `etcdutl` as the tool...

FTR: We had related discussion in https://github.com/etcd-io/etcd/pull/13902: - The fact that we load the certificate from file on every connection is enabling cert rotation, but at the same time it's...

One aspect to be aware of is also support for DNS resolution: I think that currently such connection works: ``` ./etcdctl --endpoints=http://etcd0.domain:2379,http://etcd1.domain:2379,http://etcd2.domain:2379 get k1 ``` And in case of problems...

Could you, please, create a repro in form of a test ?