NAT1TO1 and Stunner Turn Server

[Circenn5130]

I've setup a turn server in K8s via Stunner's documentation. and while it works well outside my WAN, on LAN interfaces I'm seeing traffic on the firewall routing to both the stun server and Neko's UDP ports on the pod's IP address due to the following ref, in addition to a delay in connectivity and performance.

- name: NEKO_NAT1TO1
  valueFrom:
    fieldRef:
      fieldPath: status.podIP

Which seems to be attributed to the documentation.

When I was just using UDP ports on the cluster load balancer for Neko I was able to NAT these ports appropriately for WAN and LAN, but with the turn server in place, the Neko UDP service is on a ClusterIP and I'm really not sure how I'm supposed to configure NAT1to1 so connections aren't referenced to cluster IPs outside the cluster.