-
Notifications
You must be signed in to change notification settings - Fork 619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Expand ${DC} to consul datacenter #55
Comments
The use-case as I understand it after some discussion is this: When services are accessed via fabio through their generic consul DNS name then each service has two names:
Services could discover the data center during startup and register the appropriate prefixes. However, this is not possible when registering Docker containers through registrator. By allowing to expand
|
Generating multiple routes for any number of data centers is not necessary. |
Expand the ${DC} variable in a urlprefix to the data center of the consul agent.
Expand the ${DC} variable in a urlprefix to the data center of the consul agent.
Expand the ${DC} variable in a urlprefix to the data center of the consul agent.
It is merged. |
Hi,
we need possibility to use variables like
service_name.service.$DC.$DOMAIN
in tag,so it will solve issue when having same plans for multiple datacenters and using consul domains.
This can be solved also in other way around. Adding new fabio.property use.consul.domain or tag
(to use consul domains automatically).
for example:
service:
consul
datacenters:
ams
,fra
possible consul domains:
consul.service.consul
,consul.service.ams.consul
,consul.service.fra.consul
tag:
use_consul_domain
fabio generate 3 routes:
consul.service.consul
,consul.service.ams.consul
,consul.service.fra.consul
that routes to sameconsul
serviceThe text was updated successfully, but these errors were encountered: