k3s dns only available when forwarded ports are configured

[dirtyfreebooter]

i am running a docker image not from the charts (its a proposed chart, but not currently available). Ghost blog, runs a nodejs app that listens on port 2368. i am running NGINX Proxy Manager in another container. I want to reference the Ghost blog by k3s dns name in that other container.

say my ghost container name is ghost-test. i would think i can access it via

Code:

ghost-test-ix-chart.ix-ghost-test.svc.cluster.local

but that name doesn't get registered with the k3s dns server unless i configure a port forward (any port, doesn't matter what the ports are).

because i don't want the ports exposed on NAS interface, i don't want to port forward anything, NGINX Proxy Manager can access the container via IP and port 2368.. it just that i need to use the DNS since the IP addresses are not stable on reboot...

Is there anyway to get my docker container in the k3s dns without configuring port forwarding?

 

[dirtyfreebooter]

hrmm, maybe a GUI bug? https://www.truenas.com/community/threads/inter-pod-network-communication.93399/post-668585

 

[HarryMuscle]

I just came across the same issue. Did you end up resolving your issue by any chance?

Thanks,
Harry

 

[dirtyfreebooter]

I just came across the same issue. Did you end up resolving your issue by any chance?

Thanks,
Harry

i just configured a port forward with unused port. definitely a workaround.