Open
Conversation
trapier
commented
Oct 7, 2019
|
|
||
| - Full integration with Docker (Swarm, Services, Secrets, Configs) | ||
| - Enhanced configuration (context roots, TLS, zero downtime deploy, rollback) | ||
| - Support for external load balancers (nginx, haproxy, F5, etc) via extensions |
Owner
Author
There was a problem hiding this comment.
Suggested change
| - Support for external load balancers (nginx, haproxy, F5, etc) via extensions | |
| - Support for external load balancers (NGINX, HAProxy, F5, etc) via extensions \* |
- capitalization
- caveat NGINX is the only implemented extension
trapier
commented
Oct 7, 2019
| keywords: routing, UCP, interlock, load balancing | ||
| --- | ||
|
|
||
| Application-layer (Layer 7) routing is the application routing and load balancing (ingress routing) system included with Docker Enterprise for Swarm orchestration. Interlock architecture takes advantage of the underlying Swarm components to provide scalable Layer 7 routing and Layer 4 VIP mode functionality. |
Owner
Author
There was a problem hiding this comment.
Suggested change
| Application-layer (Layer 7) routing is the application routing and load balancing (ingress routing) system included with Docker Enterprise for Swarm orchestration. Interlock architecture takes advantage of the underlying Swarm components to provide scalable Layer 7 routing and Layer 4 VIP mode functionality. | |
| Layer 7 routing is the ingress application routing and load balancing system included with Docker Enterprise for Swarm orchestration. Interlock architecture takes advantage of the underlying Swarm to provide scalable layer 7 routing for Swarm services. |
- remove parenthetical stutters
- take the application-layer marbles out of your mouth
- remove reference to layer 4. this is about layer 7, right?
- tolower Layer for consistency with subsequent use
Owner
Author
There was a problem hiding this comment.
please dear deity introduce interlock before you start talking about its architecture.
trapier
commented
Oct 7, 2019
| traffic to your Kubernetes applications, check | ||
| [layer 7 routing with Kubernetes.](../kubernetes/layer-7-routing.md) | ||
|
|
||
| Interlock uses the Docker Remote API to automatically configure extensions such as NGINX or HAProxy for application traffic. Interlock is designed for: |
Owner
Author
There was a problem hiding this comment.
Suggested change
| Interlock uses the Docker Remote API to automatically configure extensions such as NGINX or HAProxy for application traffic. Interlock is designed for: | |
| Interlock uses the Docker Remote API to automatically configure NGINX for application traffic. Interlock is designed for: |
- remove reference to HAproxy.
trapier
commented
Oct 7, 2019
|
|
||
| Interlock uses the Docker Remote API to automatically configure extensions such as NGINX or HAProxy for application traffic. Interlock is designed for: | ||
|
|
||
| - Full integration with Docker (Swarm, Services, Secrets, Configs) |
Owner
Author
There was a problem hiding this comment.
Suggested change
| - Full integration with Docker (Swarm, Services, Secrets, Configs) | |
| - Full integration with Docker Swarm (Services, Networks, Secrets, Configs) |
- scope Docker to Swarm
- note integration with networks
trapier
commented
Oct 7, 2019
| - Full integration with Docker (Swarm, Services, Secrets, Configs) | ||
| - Enhanced configuration (context roots, TLS, zero downtime deploy, rollback) | ||
| - Support for external load balancers (nginx, haproxy, F5, etc) via extensions | ||
| - Least privilege for extensions (no Docker API access) |
Owner
Author
There was a problem hiding this comment.
Suggested change
| - Least privilege for extensions (no Docker API access) | |
| - Least privilege for extensions (no Docker API access) | |
| \* NGINX is currently the only released and supported extension. |
- add caveat on supported extensions
trapier
commented
Oct 7, 2019
|
|
||
|  | ||
|
|
||
| For example, a WordPress service is listening on port 8000 of the routing mesh. Even though the service is running on a single node, users can access WordPress using the domain name or IP of any of the nodes that are part of the swarm. |
Owner
Author
There was a problem hiding this comment.
Suggested change
| For example, a WordPress service is listening on port 8000 of the routing mesh. Even though the service is running on a single node, users can access WordPress using the domain name or IP of any of the nodes that are part of the swarm. | |
| For example, a WordPress service is published to port 8000 of the ingress routing mesh. Even though the service is only running on a single node, users can access WordPress by connecting the to domain name or IP of any node in the cluster on port 8000. |
- ingress routing mesh
- fix capitalization of swarm by not using it
- use the word
portmultiple times to subtly indicate routing mesh is layer 4.
Owner
Author
There was a problem hiding this comment.
Explicitly reference layer 4 for extension by layer 7 in the next paragraph?
trapier
commented
Oct 7, 2019
|
|
||
| For example, a WordPress service is listening on port 8000 of the routing mesh. Even though the service is running on a single node, users can access WordPress using the domain name or IP of any of the nodes that are part of the swarm. | ||
|
|
||
| UCP extends this one step further with layer 7 layer routing (also known as application layer 7), allowing users to access Docker services using domain names instead of IP addresses. This functionality is made available through the Interlock component. |
Owner
Author
There was a problem hiding this comment.
Suggested change
| UCP extends this one step further with layer 7 layer routing (also known as application layer 7), allowing users to access Docker services using domain names instead of IP addresses. This functionality is made available through the Interlock component. | |
| UCP extends this one step further with layer 7 layer routing, allowing users to access Docker services using domain names instead of port numbers. This functionality is made available through the Interlock component. |
- drop the parenthetical
- correct the contrast reference to port number (i.e. layer 4)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.