Closed tiroso closed 4 months ago
Describe the bug
In case of a zabbix-proxy deployment with zabbix-agent as a sidecar, the service is pointing to zabbix-server instead of zabbix-proxy.
Version of Helm and Kubernetes:
What happened:
What you expected to happen:
The service should point to zabbix-proxy
How to reproduce it (as minimally and precisely as possible):
Just deploy zabbix-proxy instead of server and inspect the service fopr zabbix -agent
Anything else we need to know:
PR created
Describe the bug
In case of a zabbix-proxy deployment with zabbix-agent as a sidecar, the service is pointing to zabbix-server instead of zabbix-proxy.
Version of Helm and Kubernetes:
What happened:
In case of a zabbix-proxy deployment with zabbix-agent as a sidecar, the service is pointing to zabbix-server instead of zabbix-proxy.
What you expected to happen:
The service should point to zabbix-proxy
How to reproduce it (as minimally and precisely as possible):
Just deploy zabbix-proxy instead of server and inspect the service fopr zabbix -agent
Anything else we need to know:
PR created