Problems with deploying a load balancer in front of etcd clusters

Question

i am trying to deployu a load balancer in front of 3 of my etcd clusters which are running on port 2379. But I am always getting a connection refused error. I ve added firewall IPs for healthchecks and added a fw rule for 0.0.0.0 on port 2379 but still having this issue. Is deploying an internal LB to load balance to servers in backend serving on port 2379 too difficult, am I missing something ?

Anyone had this type of issue before ?

Answer 1

ok, thank you guys who contributed to my problem, here s the problem and the solution, it s because of the nature of gcp load balancers i think.

Here is the earlier etcd config and the latest config.. as soon as i changed the config, LBs started routing trrafic

Earlier:

ExecStart=/usr/local/bin/etcd \\
  --name $ETCD_NAME \\
  --discovery-srv bstock.local \\
  --initial-advertise-peer-urls http://$INTERNAL_IP:2380 \\
  --initial-cluster-token etcd-cluster-1 \\
  --initial-cluster-state new \
  --advertise-client-urls http://$INTERNAL_IP:2379 \\
  --listen-peer-urls http://$INTERNAL_IP:2380 \\
  --listen-client-urls http://$INTERNAL_IP:2379,http://127.0.0.1:2379 \\
  --data-dir=/var/lib/etcd

Latest:

ExecStart=/usr/local/bin/etcd \\
  --name $ETCD_NAME \\
  --discovery-srv bstock.local \\
  --initial-advertise-peer-urls http://$INTERNAL_IP:2380 \\
  --initial-cluster-token etcd-cluster-1 \\
  --initial-cluster-state new \
  --advertise-client-urls http://$INTERNAL_IP:2379 \\
  --listen-peer-urls http://$INTERNAL_IP:2380 \\
  --listen-client-urls http://0.0.0.0:2379 \\
  --data-dir=/var/lib/etcd