TLSRoute & UDPRoutes are not working with latest Kong Ingress controller

We have installed kong ingress controller in our eks setup and were trying the examples given in Proxy TCP requests - v3.0.x | Kong Docs for configuring TLSRoute & UDPRoute. As the gateway api functionality wasn’t working as expected, debug logs were enabled for controller and found the below logs

TLSRoute logs
2023-12-13T02:56:25Z debug controllers.TLSRoute Retrieving GatewayClass and Gateway for route {“GatewayV1Alpha2TLSRoute”: {“name”:“echo-tls”,“namespace”:“default”}, “v”: 1, “namespace”: “default”, “name”: “echo-tls”}
2023-12-13T02:56:25Z debug controllers.TLSRoute Listener does not support this route {“GatewayV1Alpha2TLSRoute”: {“name”:“echo-tls”,“namespace”:“default”}, “parentRef.gateway”: “default/kong”, “listener”: “http”, “v”: 1, “reason”: “unsupported route kind”}
2023-12-13T02:56:25Z debug controllers.TLSRoute Listener does not support this route {“GatewayV1Alpha2TLSRoute”: {“name”:“echo-tls”,“namespace”:“default”}, “parentRef.gateway”: “default/kong”, “listener”: “stream9000”, “v”: 1, “reason”: “unsupported route kind”}
2023-12-13T02:56:25Z debug controllers.TLSRoute Route’s type does not match listener’s type {“GatewayV1Alpha2TLSRoute”: {“name”:“echo-tls”,“namespace”:“default”}, “parentRef.gateway”: “default/kong”, “listener”: “stream9443”, “v”: 1, “route_name”: “echo-tls”}
2023-12-13T02:56:25Z debug controllers.TLSRoute Listener does not support this route {“GatewayV1Alpha2TLSRoute”: {“name”:“echo-tls”,“namespace”:“default”}, “parentRef.gateway”: “default/kong”, “listener”: “stream9999”, “v”: 1, “reason”: “unsupported route kind”}
2023-12-13T02:56:25Z debug controllers.TLSRoute Listener does not support this route {“GatewayV1Alpha2TLSRoute”: {“name”:“echo-tls”,“namespace”:“default”}, “parentRef.gateway”: “default/kong”, “listener”: “grpc”, “v”: 1, “reason”: “unsupported route kind”}
2023-12-13T02:56:25Z debug controllers.TLSRoute Checking if the tlsroute’s gateways are ready {“GatewayV1Alpha2TLSRoute”: {“name”:“echo-tls”,“namespace”:“default”}, “v”: 1, “namespace”: “default”, “name”: “echo-tls”}
2023-12-13T02:56:25Z debug controllers.TLSRoute Ensuring status contains Gateway associations {“GatewayV1Alpha2TLSRoute”: {“name”:“echo-tls”,“namespace”:“default”}, “v”: 1, “namespace”: “default”, “name”: “echo-tls”}
2023-12-13T02:56:25Z debug controllers.TLSRoute TLSRoute not configured,requeueing {“GatewayV1Alpha2TLSRoute”: {“name”:“echo-tls”,“namespace”:“default”}, “v”: 1, “namespace”: “default”, “name”: “echo-tls”}

UDPRoute logs
2023-12-13T02:56:25Z debug controllers.UDPRoute Processing udproute {“GatewayV1Alpha2UDPRoute”: {“name”:“tftp”,“namespace”:“udp-example”}, “v”: 1, “namespace”: “udp-example”, “name”: “tftp”}
2023-12-13T02:56:25Z debug controllers.UDPRoute Checking deletion timestamp {“GatewayV1Alpha2UDPRoute”: {“name”:“tftp”,“namespace”:“udp-example”}, “v”: 1, “namespace”: “udp-example”, “name”: “tftp”}
2023-12-13T02:56:25Z debug controllers.UDPRoute Retrieving GatewayClass and Gateway for route {“GatewayV1Alpha2UDPRoute”: {“name”:“tftp”,“namespace”:“udp-example”}, “v”: 1, “namespace”: “udp-example”, “name”: “tftp”}
2023-12-13T02:56:25Z debug controllers.UDPRoute Listener does not support this route {“GatewayV1Alpha2UDPRoute”: {“name”:“tftp”,“namespace”:“udp-example”}, “parentRef.gateway”: “default/kong”, “listener”: “http”, “v”: 1, “reason”: “unsupported route kind”}
2023-12-13T02:56:25Z debug controllers.UDPRoute Listener does not support this route {“GatewayV1Alpha2UDPRoute”: {“name”:“tftp”,“namespace”:“udp-example”}, “parentRef.gateway”: “default/kong”, “listener”: “stream9000”, “v”: 1, “reason”: “unsupported route kind”}
2023-12-13T02:56:25Z debug controllers.UDPRoute Listener does not support this route {“GatewayV1Alpha2UDPRoute”: {“name”:“tftp”,“namespace”:“udp-example”}, “parentRef.gateway”: “default/kong”, “listener”: “stream9443”, “v”: 1, “reason”: “unsupported route kind”}
2023-12-13T02:56:25Z debug controllers.UDPRoute Listener is not ready {“GatewayV1Alpha2UDPRoute”: {“name”:“tftp”,“namespace”:“udp-example”}, “parentRef.gateway”: “default/kong”, “listener”: “stream9999”, “v”: 1, “reason”: “listener not programmed yet”}
2023-12-13T02:56:25Z debug controllers.UDPRoute Listener does not support this route {“GatewayV1Alpha2UDPRoute”: {“name”:“tftp”,“namespace”:“udp-example”}, “parentRef.gateway”: “default/kong”, “listener”: “grpc”, “v”: 1, “reason”: “unsupported route kind”}
2023-12-13T02:56:25Z debug controllers.UDPRoute Checking if the udproute’s gateways are ready {“GatewayV1Alpha2UDPRoute”: {“name”:“tftp”,“namespace”:“udp-example”}, “v”: 1, “namespace”: “udp-example”, “name”: “tftp”}
2023-12-13T02:56:25Z debug controllers.UDPRoute Ensuring status contains Gateway associations {“GatewayV1Alpha2UDPRoute”: {“name”:“tftp”,“namespace”:“udp-example”}, “v”: 1, “namespace”: “udp-example”, “name”: “tftp”}
2023-12-13T02:56:25Z debug controllers.UDPRoute UDPRoute not configured,requeueing {“GatewayV1Alpha2UDPRoute”: {“name”:“tftp”,“namespace”:“udp-example”}, “v”: 1, “namespace”: “udp-example”, “name”: “tftp”}

Can you please let us know what could be reason for this behaviour?

Hi,
I’m facing a similar Issue: not beeing able to successfully using TLSRoute.

What I found so far:

  1. Check the status of your “Gateway” resource. This should tell you if the listeners are successfully configured, and which Route kinds are allowed. This changes dynamically with the config