Issue description

I saw this issue #3673 and this pr #3676.
I think it's time to enable the etcd health check feature.
by the way, etcd's host configuration, if it is in the form of ip:port, the health check takes effect, if it is in the form of domain, the health check fails because etcd's node is hidden behind the domain and cannot be distinguished, so use the FQDN of etcd in k8s does not solve the issues #3673.