Interlock is based on the ingress controller's logic described previously. Docker Swarm architecture is different. Its differences are even more pronounced when we talk about Kubernetes and Docker Swarm networking implementations. Kubernetes provides a flat network architecture, as we have seen. Multiple networks within the cluster will add additional security features, but also more complexity.
Interlock substitutes the previous Docker Enterprise's router mesh L7 routing implementation. Router mesh was available in previous UCP releases. Interlock appeared in the 2.0 release of Docker Enterprise.
Interlock will integrate Docker Swarm and Docker Remote API features to isolate and configure dynamically an application proxy such as NGINX or HA-Proxy using extensions. Interlock will use Docker Swarm's well-known objects, such as configs and secrets, to manage proxy required configurations. We will be able to...