Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Support TCPIngress with expression router #4541

Closed
1 of 2 tasks
Tracked by #4312
randmonkey opened this issue Aug 21, 2023 · 0 comments · Fixed by #4612
Closed
1 of 2 tasks
Tracked by #4312

Support TCPIngress with expression router #4541

randmonkey opened this issue Aug 21, 2023 · 0 comments · Fixed by #4612
Assignees
@rainest
Labels
area/feature New feature or request
Milestone
KIC v2.12.x

Comments

@randmonkey
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Problem Statement

Split out of #4312
Kong 3.4 added support of expression router in L4 proxy. We could implement support of TCPIngress in KIC defined CRDs: https://github.com/Kong/kubernetes-ingress-controller/blob/main/pkg/apis/configuration/v1beta1/tcpingress_types.go

Proposed Solution

  • Translate TCPIngress into expression based Kong route when ExpressionRoutes feature gate is enabled, and Kong uses expression router

Additional information

No response

Acceptance Criteria

  • KIC could translate TCPIngress to expression based Kong routes against Kong 3.4+ running with expression router
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rainest rainest

Labels
area/feature New feature or request
Projects
None yet
Milestone
KIC v2.12.x
Development

Successfully merging a pull request may close this issue.

Support TCPIngress and UDPIngress expression routes Kong/kubernetes-ingress-controller
2 participants
@rainest @randmonkey