From bc4eb8d5f0c30a4d1c05599667fee680edb8629e Mon Sep 17 00:00:00 2001 From: Victoria Bialas Date: Wed, 29 Mar 2017 23:06:15 -0400 Subject: [PATCH] added note, links re: EVERY_NODE affect on links (#2541) wording change improved wording of Tip improved wording per feedback update EVERY_NODE link description per feedback reworded per feedback Signed-off-by: Victoria Bialas --- docker-cloud/apps/service-links.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docker-cloud/apps/service-links.md b/docker-cloud/apps/service-links.md index abcb9109d0..a015c1eeb7 100644 --- a/docker-cloud/apps/service-links.md +++ b/docker-cloud/apps/service-links.md @@ -107,6 +107,14 @@ scales up or down. Service links are only updated when a service is deployed or redeployed, but are not updated during runtime. No new service link environment variables are created when a service scales up or down. +>**Tip:** You can specify one of several [container distribution strategies](/docker-cloud/infrastructure/deployment-strategies.md) for +applications deployed to multiple nodes. These strategies enable automatic +deployments of containers to nodes, and sometimes auto-linking of containers. +Note that if a service with +[EVERY_NODE](/docker-cloud/infrastructure/deployment-strategies.md#every-node) +strategy is linked to another service with EVERY_NODE strategy, containers will +be linked one-to-one on each node. + ### Service link example For the explanation of service linking, consider the following application