huangyutongs commented on issue #2668: URL: https://github.com/apache/apisix-ingress-controller/issues/2668#issuecomment-3668944924
Apisix Supports using `tcp-route` to proxy TCP traffic. https://apisix.apache.org/docs/ingress-controller/1.8.0/concepts/apisix_route/#tcp-route but The ingressPort (9100 here) should be pre-defined in the [APISIX configuration](https://github.com/apache/apisix/blob/master/conf/config.yaml.example#L76). This means I would need to modify the APISIX configuration file and restart APISIX. Restarting APISIX in a production environment would result in some traffic loss, which forced me to abandon using APISIX to proxy TCP traffic. Currently, I'm using ingress-nginx in hostnetwork mode to configure dynamic TCP proxying. With just one line of code, ingress-nginx can listen on a port and proxy to the corresponding service. ``` apiVersion: v1 kind: ConfigMap metadata: name: ingress-nginx-tcp data: "9090": monitoring/prometheus-service:9090 ``` Due to the upcoming deprecation of ingress-nginx, I switched to using ingress-haproxy, which performs just as well as ingress-controller. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
