-
Notifications
You must be signed in to change notification settings - Fork 364
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
Add Support for TCPRoute API #643
Comments
we should wait on #413 which will refactor the provider before starting this issue |
I am assigning myself, but if this is required #413, I think the finished time cannot be measured correctly. Not sure if this can be done in v0.3.0-rc1, but let us see the progress. |
@Xunzhuo suggest following the order mentioned here #641 (comment) |
Similarly to UDPRoute(#641), I think we need some design docs around the tradeoffs we'll need to make between transparent mode and proxy mode for TCP streams. The choice is basically between:
|
@youngnick we are already using the the tcp_proxy filter for TLS Passthrough which works well, and envoy only supports proxy mode for TCP (docs are here) . |
I think it's fine as long as we call out the limitation. I wouldn't be surprised if people end up wanting us to put in something about PROXY mode eventually, but that seems fine to me. |
Relates to envoyproxy#643 Relates to envoyproxy#641 Signed-off-by: Arko Dasgupta <[email protected]>
I will start to work on this, other filters implementations are blocked for the release fo v0.6.0 GWAPI. |
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions. |
Signed-off-by: bitliu <[email protected]> Fixes: #643
Description:
Add support for TCPRoute API defined here
Related #47
The text was updated successfully, but these errors were encountered: