TCP/UDP Services routing should be part of service definition, not separately defined in one central place

LarsStegman commented 9 months ago

Defining routing rules should be part of a Service definition, like http routing rules. This could be with annotations or with a ConfigMap per Service. Annotations is probably more in line with the already existing functionality for HTTP routes.

https://kubernetes.github.io/ingress-nginx/user-guide/exposing-tcp-udp-services/

Yes, #10112 but the bot is being weird

No

k8s-ci-robot commented 9 months ago

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

LarsStegman commented 8 months ago

I think an even better way would be to implement this would be to implement the Gateway API and support the TCPRoute and UDPRoute kinds.

kubernetes / ingress-nginx

TCP/UDP Services routing should be part of service definition, not separately defined in one central place #10968