If accessing this service from a different namespace than that of the etcd cluster, use the FQDN http://<cluster-name>-client.<cluster-namespace>.svc.cluster.local:2379 .

Accessing the service from outside the cluster

In order to access the client API of the etcd cluster from outside the Kubernetes cluster, we can expose a new client service of type LoadBalancer. If using a cloud provider like GKE/GCE or AWS, setting the type to LoadBalancer will automatically create the load balancer with a publicly accessible IP.

The spec for this service will use the label selector etcd_cluster: <cluster-name> to load balance the client requests over the etcd pods in our cluster.