Reverse proxy for node inside NAT network

[songoten28]

Is your feature request related to a problem? Please describe.

I apologize for my poor English skills. I have a system with the following architecture:

1 EC2 instance with a public IP running k3s-server --node-external-ip PUBLIC_IP_ADDRESS (node name: ec2-node)
1 IoT device located within the company's internal network and without a public IP (k3s-agent) (node name: iot-node)
I have successfully joined the IoT device to the EC2 instance (k3s-server).
I am using the default Traefik load balancer.

I tried deploying a Node.js server on the ec2-node and pointed the domain to the public IP ( using another server with nginx proxy_pass ) . I tested accessing this domain, and it was working.

However, when I tried deploying a Node.js server on the iot-node, I couldn't access it.

I suspect this issue is related to reverse proxy configuration.

My questions are:

If I deploy a server on a device behind a NAT network, is there a way to access it from the internet?
Is it possible for devices within different NAT networks to communicate with each other, for example, if iot-A ( service-a ) can it connect to iot-B ( service-b)?

My ingress config

My pod

My svc

My node:

Describe the solution you'd like

Describe alternatives you've considered

Additional context

I would appreciate any help.
Thank you

[brandond]

The default flannel backend is vxlan, which is not suitable for use across the public internet. If your cluster nodes are not on a shared LAN segment, you should look at https://docs.k3s.io/installation/network-options#distributed-hybrid-or-multicloud-cluster

[songoten28]

Thank you so much, maybe as my situation I will using Tailscale VPN as a sulution.