We have installed Zabbix helm chart using external postgres db to store the data, the whole setup was successful and we disabled the proxy component in helm chart at the time of deployment.
But later, we tried to deploy proxy as different helm version within the same namespace, but we always receive the following errors:
Unable to connect to Zabbix-server, connection refused.
P.S: Both the zabbix server and zabbix proxy are running as Pods in kubernetes platform. Is there any configuration on server side we need to enable so that the newly deployed zabbix-proxy will be added to zabbix-server's whitelist so that zabbix-server would accept connections from zabbix-proxy?
But later, we tried to deploy proxy as different helm version within the same namespace, but we always receive the following errors:
Unable to connect to Zabbix-server, connection refused.
P.S: Both the zabbix server and zabbix proxy are running as Pods in kubernetes platform. Is there any configuration on server side we need to enable so that the newly deployed zabbix-proxy will be added to zabbix-server's whitelist so that zabbix-server would accept connections from zabbix-proxy?