Why HAPROXY_DOMAIN ? about haproxy-consul HOT 5 OPEN

By the way, the byTag requires consul-template version 0.9.0 or more. I upgraded the Dockerfile, works great.

from haproxy-consul.

That is pretty cool.

We used the HAPROXY_DOMAIN for simplicity of deployment. By changing the var and restarting the container we could easily move cluster DNS suffixes.

from haproxy-consul.

I see, but I feel that this domain information should come from consul itself.
When consul supports metadata as mentioned in http://gliderlabs.com/registrator/latest/user/services/ (Attrs field) it will be really easy to do.

I'm not sure that you need a DNS suffix anyway, it doesn't really add security.

from haproxy-consul.

We use the DNS suffix for external traffic. First we create a wildcard dns like*.our-domain.com, and then set the HAPROXY_DOMAIN variable to "our-domain.com"

from haproxy-consul.

That's also what I did :)

from haproxy-consul.