From a35c2f77f2620afdaf0e89e8a259ffbf3b4ee1ea Mon Sep 17 00:00:00 2001 From: Maria Bermudez Date: Tue, 18 Dec 2018 12:34:23 -0800 Subject: [PATCH] Incorporate feedback from Steven --- ee/ucp/interlock/usage/index.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/ee/ucp/interlock/usage/index.md b/ee/ucp/interlock/usage/index.md index 58e7fb1b8e..a6080512b4 100644 --- a/ee/ucp/interlock/usage/index.md +++ b/ee/ucp/interlock/usage/index.md @@ -46,7 +46,9 @@ the host header, that request is forwarded to the demo service. should attach to in order to be able to communicate with the demo service. To use layer 7 routing, your services need to be attached to at least one network. If your service is only attached to a single network, you don't need to add -a label to specify which network to use for routing. To attach to more than one network, prefix this label with the stack name as shown in the above example. +a label to specify which network to use for routing. When using a common stack file for multiple deployments leveraging UCP Interlock / Layer 7 Routing, prefix `com.docker.lb.network` with the stack name to ensure traffic will be directed to the correct overlay network. + + * The `com.docker.lb.port` label specifies which port the `ucp-interlock-proxy` service should use to communicate with this demo service. * Your service doesn't need to expose a port in the swarm routing mesh. All