Skip to content

Commit

Permalink
Merge 6904973 into backport/xw-worker-docs/duly-apt-basilisk
Browse files Browse the repository at this point in the history
  • Loading branch information
hc-github-team-secure-boundary authored Jul 27, 2023
2 parents 3d18089 + 6904973 commit fbe7c34
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions website/content/docs/concepts/workers.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ across multiple networks to form reverse proxy connections between the user and

In multi-hop scenarios, there are typically three types of workers:
1. **Ingress worker** - An ingress worker is a worker that is accessible by the client. The client initiates the connection to the ingress worker.
1. **Intermediary worker** - An (optional) intermediary worker sits between ingress and egress workers as part of a multi-hop chain. There can be multiple intermediary workers as part of a multi-hop chain.
1. **Intermediary worker** - An optional intermediary worker sits between ingress and egress workers as part of a multi-hop chain. There can be multiple intermediary workers as part of a multi-hop chain.
1. **Egress worker** - An egress worker is a worker that can access the target. The egress worker initiates reverse proxy connections to intermediary or ingress workers.

<Tip>
Expand All @@ -72,7 +72,7 @@ at a time. For example in the diagram below, the intermediary worker is also an

After the persistent connection chain is established between the workers, when you attempt to connect to a target host, you are automatically proxied from:
1. Boundary client to ingress worker
1. Ingress worker to intermediary worker (where applicable)
1. Ingress worker to intermediary worker, where applicable
1. Ingress worker to egress worker
1. Egress worker to desired target

Expand Down

0 comments on commit fbe7c34

Please sign in to comment.