Add template support for network aliases

[benturner]

This is at least a piece of #2207...

[cirocosta]

👍 👍

A use-case:

• deploys a global service named svc1
• deploy a service named svc2
• from svc2 wants to contact the container from svc1 that sits on its machine (note: no ports exposed, svc1 and svc2 are in the same network)

If svc1 can template its network-alias, then it can include {{.Node.Id}} such that svc2 can use its node-id to target the svc1 instance in that machine.

[mustafaakin]

Any updates on this? Definetely useful

[iTaybb]

Any update?

[stepan-romankov]

?

[firecow]

I would also like this. Its especially useful, when running a seperate nginx and php service accross multiple nodes. And you only want nginx-node01 to hit php-node01, because you are using an external HOST loadbalancer like Cloudflare. Right now the only option I have is to make a "merged" service, using supervisord, and that doesn't seem very docker like.

[tom-x1]

I would also like to use this to run an Elasticsearch Cluster with Metricbeat

[upcFrost]

Any updates??? Using templates and making alias stick to the hostname solves a lot of problems with node-bound software like zookeeper and Kafka