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

interlock arch: fix constraint summary 

Technical:
- Neither interlock extension nor interlock proxy are constrained to worker
  nodes.

Style:
- Break up run-on sentence

testedon: UCP 3.0.4
This commit is contained in:
Trapier Marshall 2018-09-07 17:31:10 -04:00
parent f20d5af2c7
commit fcd8d3ed88
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
ee/ucp/interlock/architecture.md
View File

@ -22,9 +22,9 @@ routing in UCP:
![](../images/interlock-architecture-1.svg) ![](../images/interlock-architecture-1.svg)
An Interlock service starts running on a manager node, an Interlock-extension The Interlock service starts a single replica on a manager node. The
service starts running on a worker node, and two replicas of the Interlock-extension service runs a single replica on any available node, and
Interlock-proxy service run on worker nodes. the Interlock-proxy service starts two replicas on any available node.
If you don't have any worker nodes in your cluster, then all Interlock If you don't have any worker nodes in your cluster, then all Interlock
components run on manager nodes. components run on manager nodes.