mirror of https://github.com/docker/docs.git
Rename interlock in TOC (#414)
This commit is contained in:
Jim Galasyn
parent
a1b2624583
commit
d9d05a6ee6
|
|
@ -1701,13 +1701,13 @@ manuals:
|
|||
title: Manage secrets
|
||||
- path: /datacenter/ucp/3.0/guides/user/secrets/grant-revoke-access/
|
||||
title: Grant access to secrets
|
||||
- sectiontitle: Interlock
|
||||
- sectiontitle: Layer 7 routing
|
||||
section:
|
||||
- title: Interlock overview
|
||||
- title: Layer 7 routing overview
|
||||
path: /datacenter/ucp/3.0/guides/interlock/
|
||||
- sectiontitle: Introduction
|
||||
section:
|
||||
- title: What is Interlock
|
||||
- title: What is Layer 7 routing
|
||||
path: /datacenter/ucp/3.0/guides/interlock/intro/
|
||||
- title: Architecture
|
||||
path: /datacenter/ucp/3.0/guides/interlock/intro/architecture/
|
||||
|
|
@ -1723,7 +1723,7 @@ manuals:
|
|||
path: /datacenter/ucp/3.0/guides/interlock/install/offline/
|
||||
- sectiontitle: Configuration
|
||||
section:
|
||||
- title: Interlock
|
||||
- title: Layer 7 routing
|
||||
path: /datacenter/ucp/3.0/guides/interlock/configuration/
|
||||
- title: Service labels
|
||||
path: /datacenter/ucp/3.0/guides/interlock/configuration/service-labels/
|
||||
|
|
@ -1733,7 +1733,7 @@ manuals:
|
|||
path: /datacenter/ucp/3.0/guides/interlock/extensions/nginx/
|
||||
- title: HAProxy
|
||||
path: /datacenter/ucp/3.0/guides/interlock/extensions/haproxy/
|
||||
- sectiontitle: Deploy apps with Interlock
|
||||
- sectiontitle: Deploy apps with Layer 7 routing
|
||||
section:
|
||||
- title: Basic deployment
|
||||
path: /datacenter/ucp/3.0/guides/interlock/usage/
|
||||
|
|
|
|||
|
|
@ -1,30 +1,39 @@
|
|||
---
|
||||
title: Interlock overview
|
||||
description: Learn about Interlock, an application routing and load balancing system
|
||||
title: Layer 7 routing overview
|
||||
description: Learn about Layer 7 routing, an application routing and load balancing system
|
||||
for Docker Swarm.
|
||||
keywords: ucp, interlock, load balancing
|
||||
keywords: ucp, layer 7, routing, load balancing
|
||||
ui_tabs:
|
||||
- version: ucp-3.0
|
||||
orhigher: false
|
||||
next_steps:
|
||||
- path: ops/
|
||||
title: Updates
|
||||
- path: ops/tuning/
|
||||
title: Tuning
|
||||
---
|
||||
{% if include.version=="ucp-3.0" %}
|
||||
|
||||
Interlock is an application routing and load balancing system for Docker Swarm. It uses
|
||||
Layer 7 routing is an application routing and load balancing system for Docker Swarm. It uses
|
||||
the Docker Remote API to automatically configure extensions such as Nginx or HAProxy for
|
||||
application traffic.
|
||||
|
||||
## About
|
||||
|
||||
- [Introduction](intro/index.md)
|
||||
- [What is Interlock](intro/index.md)
|
||||
- [What is Layer 7 routing](intro/index.md)
|
||||
- [Architecture](intro/architecture.md)
|
||||
|
||||
## Deployment
|
||||
|
||||
- [Get started](install/index.md)
|
||||
- [Deploy Interlock manually](install/manual-deployment.md)
|
||||
- [Deploy Interlock offline](install/offline.md)
|
||||
- [Deploy Interlock for production](install/production.md)
|
||||
- [Deploy Layer 7 routing manually](install/manual-deployment.md)
|
||||
- [Deploy Layer 7 routing offline](install/offline.md)
|
||||
- [Deploy Layer 7 routing for production](install/production.md)
|
||||
|
||||
## Configuration
|
||||
|
||||
- [Interlock configuration](configuration/index.md)
|
||||
- [Layer 7 routing configuration](configuration/index.md)
|
||||
- [Service labels](configuration/service-labels.md)
|
||||
|
||||
## Extensions
|
||||
|
|
@ -48,3 +57,5 @@ application traffic.
|
|||
|
||||
- [Updates](ops/index.md)
|
||||
- [Tuning](ops/tuning.md)
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
---
|
||||
title: Get started with Interlock
|
||||
description: earn about Interlock, an application routing and load balancing system
|
||||
title: Get started with Layer 7 routing
|
||||
description: Learn about Layer 7 routing, an application routing and load balancing system
|
||||
for Docker Swarm.
|
||||
keywords: ucp, interlock, load balancing
|
||||
keywords: ucp, layer 7, routing, load balancing
|
||||
ui_tabs:
|
||||
- version: ucp-3.0
|
||||
orhigher: false
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: Interlock architecture
|
||||
description: Learn about Interlock, an application routing and load balancing system
|
||||
title: Layer 7 routing architecture
|
||||
description: Learn about Layer 7 routing, an application routing and load balancing system
|
||||
for Docker Swarm.
|
||||
keywords: ucp, interlock, load balancing
|
||||
ui_tabs:
|
||||
|
|
@ -21,7 +21,7 @@ The following are definitions that are used:
|
|||
- GRPC: A high-performance RPC framework
|
||||
|
||||
## Services
|
||||
Interlock runs entirely as Docker Swarm services. There are three core services
|
||||
Layer 7 routing runs entirely as Docker Swarm services. There are three core services
|
||||
in an Interlock routing layer: core, extension and proxy.
|
||||
|
||||
## Core
|
||||
|
|
@ -30,7 +30,7 @@ an upstream configuration for the extensions. This is served on a GRPC API that
|
|||
extensions are configured to access.
|
||||
|
||||
## Extension
|
||||
The extension service is a helper service that queries the Interlock GRPC API for the
|
||||
The extension service is a helper service that queries the Layer 7 routing GRPC API for the
|
||||
upstream configuration. The extension service uses this to configure
|
||||
the proxy service. For proxy services that use files such as Nginx or HAProxy the
|
||||
extension service generates the file and sends it to Interlock using the GRPC API. Interlock
|
||||
|
|
@ -40,7 +40,7 @@ then updates the corresponding Docker Config object for the proxy service.
|
|||
The proxy service handles the actual requests for the upstream application services. These
|
||||
are configured using the data created by the corresponding extension service.
|
||||
|
||||
Interlock manages both the extension and proxy service updates for both configuration changes
|
||||
Layer 7 routing manages both the extension and proxy service updates for both configuration changes
|
||||
and application service deployments. There is no intervention from the operator required.
|
||||
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
---
|
||||
title: What is Interlock
|
||||
description: Learn about Interlock, an application routing and load balancing system
|
||||
title: What is Layer 7 routing
|
||||
description: Learn about Layer 7 routing, an application routing and load balancing system
|
||||
for Docker Swarm.
|
||||
keywords: ucp, interlock, load balancing
|
||||
ui_tabs:
|
||||
|
|
@ -10,7 +10,7 @@ ui_tabs:
|
|||
|
||||
{% if include.version=="ucp-3.0" %}
|
||||
|
||||
Interlock is an application routing proxy service for Docker.
|
||||
Layer 7 routing is an application routing proxy service for Docker.
|
||||
|
||||
## Design Goals
|
||||
|
||||
|
|
@ -19,48 +19,48 @@ Interlock is an application routing proxy service for Docker.
|
|||
- Support external load balancers (nginx, haproxy, F5, etc) via extensions
|
||||
- Least privilege for extensions (no Docker API access)
|
||||
|
||||
Interlock was designed to be a first class application routing layer for Docker.
|
||||
Layer 7 routing was designed to be a first class application routing layer for Docker.
|
||||
The following are the high level features it provides:
|
||||
|
||||
## Automatic Configuration
|
||||
Interlock uses the Docker API for configuration. The user does not have to manually
|
||||
Layer 7 routing uses the Docker API for configuration. The user does not have to manually
|
||||
update or restart anything to make services available.
|
||||
|
||||
## Native Swarm Support
|
||||
Interlock is fully Docker native. It runs on Docker Swarm and routes traffic using
|
||||
Layer 7 routing is fully Docker native. It runs on Docker Swarm and routes traffic using
|
||||
cluster networking and Docker services.
|
||||
|
||||
## High Availability
|
||||
Interlock runs as Docker services which are highly available and handle failures gracefully.
|
||||
Layer 7 routing runs as Docker services which are highly available and handle failures gracefully.
|
||||
|
||||
## Scalability
|
||||
Interlock uses a modular design where the proxy service is separate. This allows an
|
||||
Layer 7 routing uses a modular design where the proxy service is separate. This allows an
|
||||
operator to individually customize and scale the proxy layer to whatever demand. This is
|
||||
transparent to the user and causes no downtime.
|
||||
|
||||
## SSL
|
||||
Interlock leverages Docker Secrets to securely store and use SSL certificates for services. Both
|
||||
Layer 7 routing leverages Docker Secrets to securely store and use SSL certificates for services. Both
|
||||
SSL termination and TCP passthrough are supported.
|
||||
|
||||
## Context Based Routing
|
||||
Interlock supports advanced application request routing by context or path.
|
||||
Layer 7 routing supports advanced application request routing by context or path.
|
||||
|
||||
## Host Mode Networking
|
||||
Interlock supports running the proxy and application services in "host" mode networking allowing
|
||||
Layer 7 routing supports running the proxy and application services in "host" mode networking allowing
|
||||
the operator to bypass the routing mesh completely. This is beneficial if you want
|
||||
maximum performance for your applications.
|
||||
|
||||
## Blue-Green and Canary Service Deployment
|
||||
Interlock supports blue-green service deployment allowing an operator to deploy a new application
|
||||
Layer 7 routing supports blue-green service deployment allowing an operator to deploy a new application
|
||||
while the current version is serving. Once traffic is verified to the new application the operator
|
||||
can scale the older version to zero. If there is a problem the operation is quickly reversible.
|
||||
|
||||
## Service Cluster Support
|
||||
Interlock supports multiple extension+proxy combinations allowing for operators to partition load
|
||||
Layer 7 routing supports multiple extension+proxy combinations allowing for operators to partition load
|
||||
balancing resources for uses such as region or organization based load balancing.
|
||||
|
||||
## Least Privilege
|
||||
Interlock supports (and recommends) being deployed where the load balancing
|
||||
Layer 7 routing supports (and recommends) being deployed where the load balancing
|
||||
proxies do not need to be colocated with a Swarm manager. This makes the
|
||||
deployment more secure by not exposing the Docker API access to the extension or proxy services.
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue