-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Envoy TLS bridging #2349
Labels
question
Questions that are neither investigations, bugs, nor enhancements
Comments
Yeah +1 to @zuercher. Envoy has configurable TLS on either the downstream/listener or upstream side of things. E.g., https://www.envoyproxy.io/docs/envoy/latest/api-v2/sds.proto.html#envoy-api-msg-downstreamtlscontext and https://www.envoyproxy.io/docs/envoy/latest/api-v2/sds.proto.html#upstreamtlscontext. |
Closing out. Please let us know if you have further questions. |
Shikugawa
pushed a commit
to Shikugawa/envoy
that referenced
this issue
Mar 28, 2020
jpsim
pushed a commit
that referenced
this issue
Nov 28, 2022
Description: Previously, gzip decompression was always enabled in base configuration. This makes both gzip and brotli decompression configurable, with gzip defaulting to on (as it was previously) and brotli defaulting to off. No changes to usage of EngineBuilder need to be made to maintain existing behavior. Risk Level: Moderate Testing: Added config coverage. Signed-off-by: Mike Schore <mike.schore@gmail.com> Signed-off-by: JP Simard <jp@jpsim.com>
jpsim
pushed a commit
that referenced
this issue
Nov 29, 2022
Description: Previously, gzip decompression was always enabled in base configuration. This makes both gzip and brotli decompression configurable, with gzip defaulting to on (as it was previously) and brotli defaulting to off. No changes to usage of EngineBuilder need to be made to maintain existing behavior. Risk Level: Moderate Testing: Added config coverage. Signed-off-by: Mike Schore <mike.schore@gmail.com> Signed-off-by: JP Simard <jp@jpsim.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
This is a getting started question rather than an issue. I'm looking to implement Envoy to secure service-to-service communication between two services. A little bit like this:
Could you point me at some examples or documentation that can get me started with this if there is such a thing.
Thanks
The text was updated successfully, but these errors were encountered: