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.

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

Deprecate and remove TCP/UDP forwarding #11666

Closed
rikatz opened this issue Jul 21, 2024 · 6 comments
Closed

Deprecate and remove TCP/UDP forwarding #11666

rikatz opened this issue Jul 21, 2024 · 6 comments
Labels
kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@rikatz
Copy link
Contributor

rikatz commented Jul 21, 2024

Ingress API was originally built to allow routing of HTTP (L7) traffic. Due the time, some additional features, like supporting TCP and UDP forwarding has been added.

The maintenance of these APIs became a burden to migrate to NJS, and created a bunch of different issues on ingress-nginx. Officially, the way to route TCP/UDP traffic on a Kubernetes cluster should be made on 2 different ways:

  • Using a Service (generally of type LoadBalancer or NodePort)
  • Using GatewayAPI TCPRoute

As part of the GatewayAPI evolution, I would like to deprecate and remove TCP and UDP forwarding from current ingress-nginx as part of the next minor release and focus the current ingress-nginx implementation on L7/HTTP routing.

/kind deprecation

@k8s-ci-robot k8s-ci-robot added the kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. label Jul 21, 2024
@k8s-ci-robot
Copy link
Contributor

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. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority labels Jul 21, 2024
@aojea
Copy link
Member

aojea commented Jul 21, 2024

/cc @aojea @robscott

@tao12345666333
Copy link
Member

We do encounter a lot of TCP/UDP related questions in our issues list and user channel.

https://github.com/kubernetes/ingress-nginx/issues?page=2&q=is%3Aissue+is%3Aopen+tcp

@rikatz
Copy link
Contributor Author

rikatz commented Jul 22, 2024

Yes, but it doesn't mean we should be supporting it :)

@Gacko Gacko changed the title Deprecate and Remove TCP/UDP forwarding Deprecate and remove TCP/UDP forwarding Jul 22, 2024
Copy link

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.

@strongjz
Copy link
Member

This is a low priority and most likely will not make the cut to deprecations.

This functionality will be implemented in InGate and the Gateway API, not in ingress.

More details here https://www.youtube.com/watch?v=KLwsV6_DntA

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/deprecation Categorizes issue or PR as related to a feature/enhancement marked for deprecation. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Development

No branches or pull requests

5 participants