Open rummens opened 1 month ago
didn't you think that's a Container (configuration) issue?
from my sight of view z2m is unable to fix your problem
If it would be the DNS resolution from within the container should not work but it clear does. Thats the thing that confuses me. Is there any layer between the "OS" part of the container and the NodeJS Application that would need additional config?
What happened?
Hi there, I am setting up Z2M on my new OpenShift SNO and I ran into a small issue resolving the MQTT service. It seems no matter what I do the node.js app of Z2M is not able to resolve the K8s internal DNS record. I tried with/without port, prefix and a bunch of permutations but nothing except a straight IP seems to be accepted. This is of course not ideal in the highly flexible nature of K8s.
Hope the outputs below help, as I am no expert in node I wasn't really sure if I can tell it somehow to use another way of resolving DNS. None of the standard search methods gave me any useful hints unfortunately.
Appreciate any help Marcel
Helm Chart Config:
nslookup in the Pod confirms that DNS is correctly working:
The Pods output (error can be seen at the end):
Resolve conf looks good:
What did you expect to happen?
Application uses Pod DNS Config correctly.
How to reproduce it (minimal and precise)
Specify Cluster internal DNS entry for the MQTT Server.
Zigbee2MQTT version
1.37.1 commit: ea39d86
Adapter firmware version
7.4.3 [GA]
Adapter
ember
Setup
OpenShift SNO with Helm Chart
Debug log
zigbee2mqtt.txt