-
Notifications
You must be signed in to change notification settings - Fork 679
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
Support TLSRoute #3440
Comments
Is this part of the v1.15 in any way? We can always push it out to next release if needed. tagging it first |
I'd rate this as nice-to-have for 1.15, rather than must-have. |
Seems like this is going to move to 1.16? |
Agreed. |
Add support for TLSRoute to enable Passthrough TCP Proxying to pods via SNI. Updates projectcontour#3440 Signed-off-by: Steve Sloka <slokas@vmware.com>
Add support for TLSRoute to enable Passthrough TCP Proxying to pods via SNI. Updates projectcontour#3440 Signed-off-by: Steve Sloka <slokas@vmware.com>
Add support for TLSRoute to enable Passthrough TCP Proxying to pods via SNI. Updates projectcontour#3440 Signed-off-by: Steve Sloka <slokas@vmware.com>
Add support for TLSRoute to enable Passthrough TCP Proxying to pods via SNI. Updates projectcontour#3440 Signed-off-by: Steve Sloka <slokas@vmware.com>
Add support for TLSRoute to enable Passthrough TCP Proxying to pods via SNI. Updates projectcontour#3440 Signed-off-by: Steve Sloka <slokas@vmware.com>
Add support for TLSRoute to enable Passthrough TCP Proxying to pods via SNI. Updates projectcontour#3440 Signed-off-by: Steve Sloka <slokas@vmware.com>
Add support for TLSRoute to enable Passthrough TCP Proxying to pods via SNI. Updates projectcontour#3440 Signed-off-by: Steve Sloka <slokas@vmware.com>
Add support for TLSRoute to enable Passthrough TCP Proxying to pods via SNI. Updates projectcontour#3440 Signed-off-by: Steve Sloka <slokas@vmware.com>
Add support for TLSRoute to enable Passthrough TCP Proxying to pods via SNI. Updates projectcontour#3440 Signed-off-by: Steve Sloka <slokas@vmware.com>
Add support for TLSRoute to enable Passthrough TCP Proxying to pods via SNI. Updates #3440 Signed-off-by: Steve Sloka <slokas@vmware.com>
Some support implemented in 1.16, but completion will need to be in 1.17. |
Implements support for GatewayAPI TLSRoute mode: terminate which terminates TLS at the Gateway. Updates projectcontour#3440 Signed-off-by: Steve Sloka <slokas@vmware.com>
Implements support for GatewayAPI TLSRoute mode: terminate which terminates TLS at the Gateway. Updates projectcontour#3440 Signed-off-by: Steve Sloka <slokas@vmware.com>
Implements support for GatewayAPI TLSRoute mode: terminate which terminates TLS at the Gateway. Updates projectcontour#3440 Signed-off-by: Steve Sloka <slokas@vmware.com>
Implements support for GatewayAPI TLSRoute mode: terminate which terminates TLS at the Gateway. Updates #3440 Signed-off-by: Steve Sloka <slokas@vmware.com>
Hmm, this is partially implemented, so I'll move it to 1.18. |
@stevesloka I can take this over if that works for you, looks like still several TODOs |
I'll see if there's an opportunity for some reuse between |
Go for it! =) |
Add support for weighted ForwardTos in TLSRoute rules. Per spec, weights default to 1 if unspecified, and weights of 0 mean no traffic is forwarded to the backend. Updates projectcontour#3440. Signed-off-by: Steve Kriss <krisss@vmware.com>
Add support for weighted ForwardTos in TLSRoute rules. Per spec, weights default to 1 if unspecified, and weights of 0 mean no traffic is forwarded to the backend. Updates projectcontour#3440. Signed-off-by: Steve Kriss <krisss@vmware.com>
Add support for weighted ForwardTos in TLSRoute rules. Per spec, weights default to 1 if unspecified, and weights of 0 mean no traffic is forwarded to the backend. Updates projectcontour#3440. Signed-off-by: Steve Kriss <krisss@vmware.com>
Adds test coverage for the matching of TLSRoutes with Gateways. Updates projectcontour#3440. Signed-off-by: Steve Kriss <krisss@vmware.com>
Add support for weighted ForwardTos in TLSRoute rules. Per spec, weights default to 1 if unspecified, and weights of 0 mean no traffic is forwarded to the backend. Updates #3440. Signed-off-by: Steve Kriss <krisss@vmware.com>
Adds test coverage for the matching of TLSRoutes with Gateways. Updates projectcontour#3440. Signed-off-by: Steve Kriss <krisss@vmware.com>
Adds test coverage for the matching of TLSRoutes with Gateways. Updates #3440. Signed-off-by: Steve Kriss <krisss@vmware.com>
Task list is complete so I'm closing this out, can open new issues if we find any other gaps. |
//ref: https://gateway-api.sigs.k8s.io/spec/#networking.x-k8s.io/v1alpha1.TLSRoute
The text was updated successfully, but these errors were encountered: