I'm currently developing the etcd client for the new L4LB. I wanted to avoid hardcoding conftool hostnames by leveraging the DNS descovery features included in the etcd client but I'm getting the following error:
vgutierrez@lvs6001:~$ ./l4lb etcd --domain eqiad.wmnet 2022/10/10 11:16:02 dns lookup errors: lookup _etcd-client-ssl-conftool._tcp.eqiad.wmnet on 10.3.0.1:53: no such host and lookup _etcd-client-conftool._tcp.eqiad.wmnet on 10.3.0.1:53: no such host
Per https://etcd.io/docs/v3.3/op-guide/clustering/#dns-discovery it seems like _etcd-client and _etcd-client-ssl SRV records should be created:
To help clients discover the etcd cluster, the following DNS SRV records are looked up in the listed order: _etcd-client._tcp.example.com _etcd-client-ssl._tcp.example.com If _etcd-client-ssl._tcp.example.com is found, clients will attempt to communicate with the etcd cluster over SSL/TLS.