From cdc8b16d69a3ee97b4df7e29ae6864aafa3798cb Mon Sep 17 00:00:00 2001 From: gprossliner Date: Fri, 28 Jun 2019 12:31:18 +0200 Subject: [PATCH] Update index.md See issue #9001 for details. --- ee/ucp/interlock/usage/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ee/ucp/interlock/usage/index.md b/ee/ucp/interlock/usage/index.md index ccdf7bcb33..1e64529afc 100644 --- a/ee/ucp/interlock/usage/index.md +++ b/ee/ucp/interlock/usage/index.md @@ -101,7 +101,7 @@ 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. 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. +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. When using in combination with `com.docker.lb.ssl_passthrough` the label in mandatory, even if your service is only attached to a single 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