Open michaelbeaumont opened 1 year ago
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed. If you think this issue is still relevant, please comment on it or attend the next triage meeting.
@lukidzi did anything change here with MeshPassthrough
?
@slonka No this is just a gateway and routing feature where TLS traffic isn't terminated but still routed to in-mesh backends based on SNI.
Wasn't there a discussion in GatewayAPI about support of TLSRoute?
Description
After #6132, it should be possible to further route traffic to a passthrough TLS listener based on SNI like
TLSRoute