Skip to content

Enhance HTTP IR to support GRPCRoute#666

Merged
arkodg merged 1 commit intoenvoyproxy:mainfrom
arkodg:grpc-ir
Nov 9, 2022
Merged

Enhance HTTP IR to support GRPCRoute#666
arkodg merged 1 commit intoenvoyproxy:mainfrom
arkodg:grpc-ir

Conversation

@arkodg
Copy link
Copy Markdown
Contributor

@arkodg arkodg commented Oct 31, 2022

Relates to #642

Signed-off-by: Arko Dasgupta arko@tetrate.io

Relates to envoyproxy#642

Signed-off-by: Arko Dasgupta <arko@tetrate.io>
@arkodg arkodg requested a review from a team as a code owner October 31, 2022 23:47
@codecov-commenter
Copy link
Copy Markdown

Codecov Report

Merging #666 (37381a4) into main (592863a) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #666      +/-   ##
==========================================
- Coverage   62.82%   62.79%   -0.04%     
==========================================
  Files          47       47              
  Lines        5762     5762              
==========================================
- Hits         3620     3618       -2     
  Misses       1912     1912              
- Partials      230      232       +2     
Impacted Files Coverage Δ
internal/ir/xds.go 82.50% <ø> (ø)
internal/provider/kubernetes/gateway.go 49.68% <0.00%> (-2.56%) ⬇️
internal/provider/kubernetes/gatewayclass.go 73.18% <0.00%> (-2.18%) ⬇️
internal/provider/kubernetes/tlsroute.go 59.47% <0.00%> (+5.72%) ⬆️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@danehans
Copy link
Copy Markdown
Contributor

danehans commented Nov 1, 2022

@arkodg can you provide additional context on how this change supports GRPCRoute?

From Envoy's gRPC docs:

At the transport layer it uses HTTP/2 or above for request/response multiplexing.

Does this mean gRPC-Web will not be supported for GRPCRoute?

@arkodg
Copy link
Copy Markdown
Contributor Author

arkodg commented Nov 1, 2022

@arkodg can you provide additional context on how this change supports GRPCRoute?

From Envoy's gRPC docs:

At the transport layer it uses HTTP/2 or above for request/response multiplexing.

Does this mean gRPC-Web will not be supported for GRPCRoute?

  • this knob could be used to filter for h2 and h2c upstream connections in the listener and will mainly be used to add some more fields in the cluster so the upstream connection is http2
  • this sadly won't support grpc-web, I think of that feature as a seperate transcoding feature,
    we might be able to bundle it up and also enable grpc-web on the same downstream connection if the grpc web filter allows grpc traffic to flow through seamlessly
    @lizan do have any datapoints around this ?

@arkodg arkodg added this to the 0.3.0-rc.1 milestone Nov 7, 2022
@arkodg arkodg added the area/ir Issues related to Gateway's internal representation, e.g. data model. label Nov 7, 2022
@arkodg arkodg requested a review from danehans November 7, 2022 21:30
@arkodg arkodg merged commit 13875fa into envoyproxy:main Nov 9, 2022
@arkodg arkodg deleted the grpc-ir branch November 9, 2022 16:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/ir Issues related to Gateway's internal representation, e.g. data model.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants