This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 277
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
envoy/lds: Make outbound HTTP filter chain specific to HTTP traffic (#…
…2101) Currently, OSM only supports HTTP protocol, and as such the outbound filter chain is specific to HTTP (via the HTTP filter). This change renames the function and adds an additional filter chain match criteria to the HTTP filter chain to be specific to HTTP protocols that the downstream client is allowed to use for HTTP requests. Since OSM only supports non TLS based HTTP request origination for in-mesh traffic, the supported protocols are http/1.0, http/1.1, h2c (HTTP2 without TLS, ex. grpc.Insecure()). HTTP2 over TLS (h2) is not supported since OSM requires clients create HTTP requests over plaintext, with OSM providing mTLS capability via proxy-proxy communication. The additional filter chain matching based on application protocols should not affect the egress filter, given that destination IP has a higher precedence over application protocols in the filter chain match order. Egress traffic will not match the outbound mesh filter chain because the destination IP of egress traffic will not be a part of the in-mesh destination prefixes that get programmed in the mesh filter chain. This change is in preparation for supporting TCP traffic as a part of #1521. Signed-off-by: Shashank Ram <shashank08@gmail.com>
- Loading branch information
1 parent
b58a44f
commit 68ab84d
Showing
3 changed files
with
50 additions
and
12 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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