Tunnel TCP traffic through cloudflared?

[giannoug]

I'm still figuring out things and just ported (a simple version) of traccar on my cluster. Any ideas how can I access the TCP ports needed outside my network? For example some GPS trackers require IP/port combo.

With a quick Google search I can see this is possible, but testing with the traccar Android app and my hostname doesn't seem to work. Of course, ingress is working fine and I can access the web UI

[giannoug]

I can see a config.yaml that has some cloudflared configuration with the following contents:

---
originRequest:
  http2Origin: true

ingress:
  - hostname: "${SECRET_DOMAIN}"
    service: https://nginx-external-controller.networking.svc.cluster.local:443
    originRequest:
      originServerName: "external.${SECRET_DOMAIN}"
  - hostname: "*.${SECRET_DOMAIN}"
    service: https://nginx-external-controller.networking.svc.cluster.local:443
    originRequest:
      originServerName: "external.${SECRET_DOMAIN}"
  - service: http_status:404

The easiest guess is that I need to define my service here and it "should" work (unless I need to change more configs)

[giannoug]

Or maybe have nginx do TCP/UDP ingress? 🤔 I can see that's possible: https://kubernetes.github.io/ingress-nginx/user-guide/exposing-tcp-udp-services/

[onedr0p]

Maybe this helps? I haven't had a need to expose tcp or udp over cloudflare tunnels

https://developers.cloudflare.com/cloudflare-one/connections/connect-networks/configure-tunnels/local-management/configuration-file/#supported-protocols

[giannoug]

I gave up since my GPS trackers require a static IP to function. They only resolve hostnames when setting up, and then use the IP. If anyone ever lands here, my approach (also mentioned by @onedr0p) was the "correct" one. Keep in mind that you must use a different hostname for each service you expose