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