diff options
| author | mo khan <mo@mokhan.ca> | 2025-05-26 17:18:37 -0600 |
|---|---|---|
| committer | mo khan <mo@mokhan.ca> | 2025-05-26 17:18:37 -0600 |
| commit | 2453cfe4d9ae1b16a0233d412aa5ef3b57585b16 (patch) | |
| tree | 09bab017ac430786091f77618f3db5c57335c53d /share | |
| parent | d5933faef4b4b773e053a2e11bf3131dac407500 (diff) | |
docs: fix title and add overview subheading
Diffstat (limited to 'share')
| -rw-r--r-- | share/man/ENVOY.md | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/share/man/ENVOY.md b/share/man/ENVOY.md index 1dd8953..bfa2f26 100644 --- a/share/man/ENVOY.md +++ b/share/man/ENVOY.md @@ -1,4 +1,6 @@ -# Envoy +# Envoy Proxy + +## Overview Envoy Proxy is described as an edge and service proxy. This means that Envoy can take care of managing inbound and outbound networks requests @@ -19,7 +21,7 @@ in plugins to handle things like: Envoy can be run in multiple ways and seems to work best when working as a sidecar process to your application. The idea behind this is that you would -expose envoy to the externally and use it to reverse proxy requests to your +expose envoy to externally and use it to reverse proxy requests to your application that is only accessible via envoy. This is typically configured using a loopback address for tcp connections. Envoy can speak gRPC and HTTP quite fluently and the Envoy documentation is fairly extensive. @@ -643,3 +645,4 @@ authentication/authorization strategy that GitLab as a whole supports. * https://gitlab.com/gitlab-org/software-supply-chain-security/authorization/sparkled/-/merge_requests/7 * https://gitlab.com/gitlab-org/software-supply-chain-security/authorization/sparkled/-/merge_requests/8 * https://gitlab.com/gitlab-org/software-supply-chain-security/authorization/sparkled/-/merge_requests/9 + |