Good afternoon.
I am currently running Zabbix 7.0.2 in a Kubernetes cluster. This main instance if Zabbix has a proxy sitting in a DMZ that has DNS names that is only resolvable withing that network. If I create a HTTP agent item that talks to the OpenShift cluster via its URL it all works well and the hostname gets resolved. If I do the same with a preprocessing JavaScript step it is unable to resolve the host name which makes me believe it could be possible that the preprocessing step is not being executed on the proxy but rather on the main instance of Zabbix. This almost feels similar to ZBX-24800. Is anyone experiencing the same? If so, is there perhaps any work arounds or another fix in the pipeline?
Thank you.
I am currently running Zabbix 7.0.2 in a Kubernetes cluster. This main instance if Zabbix has a proxy sitting in a DMZ that has DNS names that is only resolvable withing that network. If I create a HTTP agent item that talks to the OpenShift cluster via its URL it all works well and the hostname gets resolved. If I do the same with a preprocessing JavaScript step it is unable to resolve the host name which makes me believe it could be possible that the preprocessing step is not being executed on the proxy but rather on the main instance of Zabbix. This almost feels similar to ZBX-24800. Is anyone experiencing the same? If so, is there perhaps any work arounds or another fix in the pipeline?
Thank you.