gateway
gateway copied to clipboard
add support for TLSRoute / TLS listener protocol / TLS passthrough
https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.ProtocolType https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1beta1.TLSModeType https://gateway-api.sigs.k8s.io/references/spec/#gateway.networking.k8s.io/v1alpha2.TLSRoute
Note, we already have TLS termination implemented (I forgot this was already implemented when discussing at this morning's meeting), so this issue is specifically for TLS passthrough, which requires the use of TLSRoute. This does seem to be a core conformance feature, despite TLSRoute remaining an alpha resource, but there are not currently conformance tests for it.
thanks for raising this issue @skriss, going forward it would be good to cross reference any GH issues in the Gateway API repo or create new ones in the Gateway API repo to address the need for validating a specific feature using Gateway API conformance tests . Lets try and use the Gateway API Conformance tests for all end to end testing, until we cannot :)
Could I take it up please. I have some idea of the changes required. thanks
we should run the upstream conformance test in CI once its added ( tracked via https://github.com/kubernetes-sigs/gateway-api/issues/1452)