I'm working with Kubernetes where my goal is to deploy multiple Zabbix proxies inside the cluster for load balancing. Currently, the Helm Chart uses a fixed name and a fixed count for the amount of replicas inside the Zabbix proxy Deployment which prevents me from starting multiple proxies in the same namespace (naming conflict). The fixed name applies for the Zabbix agent DaemonSet but is not relevant for my use-case.

metadata:
  name: zabbix-proxy // fixed name
  labels:
    app: zabbix
    tier: proxy
spec:
  selector:
    matchLabels:
      name: zabbix-proxy
  replicas: 1 // fixed replicas

Steps to reproduce:

1. Install a Chart release in namespace "xyc" with agent and proxy enabled 
2. Install a second Chart release in namespace "xyc" with proxy only enabled

Result:
Naming conflict when trying to deploy a second Chart release in the same namespace.
**

Expected:
I'd expect to start multiple proxies by either increasing the replica count via values.yaml or to install 1-n Chart releases without any conflicts. From my point of view the proxy and agent should derive the name (and related properties) from the helper macros that include Release names like the other components do.

Maybe this is not intended to work like I imagine it? If so, what would be your recommended approach? Use different namespaces for each proxy?

I do know that I can download and modify the chart myself but I'd rather have this options built in to the official chart.