Support L4 proxy CRDs in ExpressionRoutes mode

[randmonkey]

Is there an existing issue for this?

• I have searched the existing issues

Problem Statement

Kong gateway will implement L4 proxy support of expressions router: Kong/kong#11071. When the Kong gateway part is finished, KIC should start to support the CRDs to specify L4 proxy configurations. The following CRDs are included:

• TCPIngress
• UDPIngress
• TCPRoute
• TLSRoute
• UDPRoute

Proposed Solution

When ExpressionRoutes feature gate is enabled, and Kong gateway runs expressions router:

• Translate the L4 proxy CRDs to expression based Kong routes if Kong gateway supports L4 proxy with expressions based router.
• Otherwise, still disable translation of L4 proxy CRDs.

Additional information

No response

Acceptance Criteria

• When Kong gateway supports L4 proxy in expression router, KIC translates the L4 proxy CRDs correctly
  • included CRDs: TCPIngres, UDPIngress, TCPRoute, UDPRoute, TLSRoute
• when Kong gateway does not support them, still disable translation of the CRDs.

Tasks

Beta Give feedback

1. Support UDPRoute with expression router #4539
   area/gateway-api +1
   
2. Support TLSRoute with expression router #4540
   area/gateway-api +1
3. Support TCPIngress with expression router #4541
   area/feature +1
   
4. Support UDPIngress with expression router #4542
   area/feature +1
   

[mflendrich]

Blocked by Kong/kong#11538 being released in Gateway 3.4.1

[randmonkey]

close this since ALL CRDs are supported now.