bug: can't view TCP route in the dashboard.

[DevBey]

Current Behavior

TCP route created using kubectl apply should appear in the dashboard. can see the upstream service but not in routes.

Expected Behavior

the TCP route should appear in routes created using this

https://apisix.apache.org/docs/ingress-controller/concepts/apisix_route/#tcp-route

Error Logs

No response

Steps to Reproduce

1. install Apisix gateway using helm with port exposed 5432 and exposed NLB.
2. create a TCP route for exposing postgres using https://apisix.apache.org/docs/ingress-controller/concepts/apisix_route/#tcp-route.
3. the NLB:5432 does work without any issues.
4. but can't see the route in the dashboard, though upstream is visible.

Environment

• APISIX version (run apisix version): 3.9.0
• Operating system (run uname -a): kubernetes
• OpenResty / Nginx version (run openresty -V or nginx -V):
• etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
• APISIX Dashboard version, if relevant: 3.0.0
• Plugin runner version, for issues related to plugin runners:
• LuaRocks version, for installation issues (run luarocks --version):

[hanqingwu]

I think ingress route is different from route in dashboard. this is a proxy mode.

https://github.com/apache/apisix/blob/5319503293c41cf41a2caa5cb944a12d40686c83/conf/config-default.yaml#L76

  proxy_mode: http
  # stream_proxy:                 # TCP/UDP L4 proxy
  #   tcp:
  #     - addr: 9100              # Set the TCP proxy listening ports.
  #       tls: true
  #     - addr: "127.0.0.1:9101" 

[DevBey]

oh ok,

thanks @hanqingwu.

is there any way to check that on the dashboard ??

[hanqingwu]

Sorry, Not currently supported

[DevBey]

no worries thanks for the quick response.

a quick feedback would be that we need to improve the dashboard, it lags way behind something like kong.

currently, when deciding on which gateway to go with, dashboard seems very disappointing.

should we keep this open or close it ??

[hanqingwu]

@shreemaan-abhishek