You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
updated Layer 7 UI image to have correct http port, updated deployment steps to make it clear what can be done via the UI and the alternative manualy approach
Copy file name to clipboardExpand all lines: ee/ucp/interlock/deploy/index.md
+20-12Lines changed: 20 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,27 +8,30 @@ redirect_from:
8
8
9
9
This topic covers deploying a layer 7 routing solution into a Docker Swarm to route traffic to Swarm services. Layer 7 routing is also referred to as an HTTP routing mesh.
By default, the routing mesh service listens on port 8080 for HTTP and port
34
37
8443 for HTTPS. Change the ports if you already have services that are using
@@ -55,8 +58,7 @@ start the `ucp-interlock-proxy` service.
55
58
At this point everything is ready for you to start using the layer 7 routing
56
59
service with your swarm workloads.
57
60
58
-
59
-
The following code sample provides a default UCP configuration:
61
+
The following code sample provides a default UCP configuration (this will be created automatically when enabling Interlock as per section [Enable layer 7 routing](#enable-layer-7-routing)):
Interlock can also be enabled from the command line by following the below setions.
131
+
126
132
### Work with the core service configuration file
133
+
127
134
Interlock uses the TOML file for the core service configuration. The following example utilizes Swarm deployment and recovery features by creating a Docker Config object:
0 commit comments