docker
/
docs
mirror of https://github.com/docker/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

interlock: Remove `com.docker.lb.ssl_only` config label (#1135) 

* interlock: Remove `com.docker.lb.ssl_only` config label and service-lables file (moved to labels-reference.md)

* Update labels-reference.md
This commit is contained in:
Euan Harris 2019-06-06 12:35:13 +01:00 committed by paigehargrave
parent 38636dec3a
commit fcb2886a05
3 changed files with 19 additions and 46 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
_data/toc.yaml
View File

@ -1331,8 +1331,6 @@ manuals:
path: /ee/ucp/interlock/config/host-mode-networking/
- title: Configuring an nginx extension
path: /ee/ucp/interlock/config/nginx-config/
- title: Using application service labels
path: /ee/ucp/interlock/config/service-labels/
- title: Tuning the proxy service
path: /ee/ucp/interlock/config/tuning/
- title: Updating Interlock services

43
ee/ucp/interlock/config/service-labels.md
View File

@ -1,43 +0,0 @@
---
title: Use application service labels
description: Learn how applications use service labels for publishing
keywords: routing, proxy, interlock, load balancing
---
Service labels define hostnames that are routed to the
service, the applicable ports, and other routing configurations. Applications that publish using Interlock use service labels to configure how they are published.
When you deploy or update a swarm service with service labels, the following actions occur:
1. The `ucp-interlock` service monitors the Docker API for events and
publishes the events to the `ucp-interlock-extension` service.
2. That service then generates a new configuration for the proxy service,
based on the labels you added to your services.
3. The `ucp-interlock` service takes the new configuration and reconfigures the
`ucp-interlock-proxy` to start using the new configuration.
The previous steps occur in milliseconds and with rolling updates. Even though
services are being reconfigured, users won't notice it.
## Service label options
The following table describes the available options:
| Label | Description | Example |
| --- | --- | --- |
| `com.docker.lb.hosts` | Comma separated list of the hosts that the service should serve | `example.com,test.com` |
| `com.docker.lb.port` | Port to use for internal upstream communication | `8080` |
| `com.docker.lb.network` | Name of network the proxy service should attach to for upstream connectivity | `app-network-a` |
| `com.docker.lb.context_root` | Context or path to use for the application | `/app` |
| `com.docker.lb.context_root_rewrite` | Boolean to enable rewrite for the context root | `true` |
| `com.docker.lb.ssl_only` | Boolean to force SSL for application | `true` |
| `com.docker.lb.ssl_cert` | Docker secret to use for the SSL certificate | `example.com.cert` |
| `com.docker.lb.ssl_key` | Docker secret to use for the SSL key | `example.com.key` |
| `com.docker.lb.websocket_endpoints` | Comma separated list of endpoints to configure to be upgraded for websockets | `/ws,/foo` |
| `com.docker.lb.service_cluster` | Name of the service cluster to use for the application | `us-east` |
| `com.docker.lb.ssl_backend` | Enable SSL communication to the upstreams | `true` |
| `com.docker.lb.ssl_backend_tls_verify` | Verification mode for the upstream TLS | `none` |
| `com.docker.lb.sticky_session_cookie` | Cookie to use for sticky sessions | `none` |
| `com.docker.lb.redirects` | Semi-colon separated list of redirects to add in the format of `<source>,<target>`. Example: (`http://old.example.com,http://new.example.com;`) | `none` |
| `com.docker.lb.ssl_passthrough` | Enable SSL passthrough | `false` |
| `com.docker.lb.backend_mode` | Select the backend mode that the proxy should use to access the upstreams. Defaults to `task`. | `vip` |

20
ee/ucp/interlock/usage/labels-reference.md
View File

@ -2,12 +2,30 @@
title: Use layer 7 routing labels
description: Learn about the labels you can use in your swarm services to route
layer 7 traffic.
keywords: routing, proxy
redirect_from:
- /ee/ucp/interlock/config/service-labels/
keywords: routing, proxy, interlock, load balancing
---
After you enable the layer 7 routing solution, you can
[start using it in your swarm services](index.md).
Service labels define hostnames that are routed to the
service, the applicable ports, and other routing configurations. Applications that publish using Interlock use service labels to configure how they are published.
When you deploy or update a swarm service with service labels, the following actions occur:
1. The `ucp-interlock` service monitors the Docker API for events and
publishes the events to the `ucp-interlock-extension` service.
2. That service then generates a new configuration for the proxy service,
based on the labels you added to your services.
3. The `ucp-interlock` service takes the new configuration and reconfigures the
`ucp-interlock-proxy` to start using the new configuration.
The previous steps occur in milliseconds and with rolling updates. Even though
services are being reconfigured, users won't notice it.
## Service label options
| Label | Description | Example |
|:---------------------------------------|:-----------------------------------------------------------------------------------------------------------------------------------------------|:-----------------------|