templates/service.yaml hardcodes the pod selector to a single label of "name: zabbix-proxy".

  selector:
    name: zabbix-proxy

This is adequate for single-proxy configurations (the most common use case), but this does not scale to environments where the admin desires multiple proxies that within the same Kubernetes cluster. Some example use cases:

• multiple instances of Zabbix managed by different teams
• isolating metrics by traffic origin to specific proxies
• running multiple proxies in order to isolate proxy loads from each other

Installation of multiple proxy workloads can be achieved by installing the Helm chart multiple times, with each installation being given its own release name if they are being installed into the same namespace. The problem with the current helm chart is that the templates for the Deployment and Service manifests hardcode an arbitrary label selector. All Pods will have identical labels, and the generated Service objects will end up routing traffic to all pods with a label of "name: zabbix-proxy".

Support for this functionality would require the following changse:

• amend templates/zabbix-proxy.yaml and templates/service.yaml to support user defined labels
• exposing the new variable for user defined labels in values.yaml.