Unable to install multiple Weaviate clusters in same namespace

[samos123]

The templates hardcode a resource name instead of relying on the helm release name. So when you try to deploy another weaviate cluster it would fail because there is already a statefulset named weaviate.

I propose to instead use this format for all resources:

kind: StatefulSet     
metadata:     
  name: "{{ .Release.Name }}-weaviate"     
  labels:                                                                                                             
    name: "{{ .Release.Name }}-weaviate"                                                                          
    app: "{{ .Release.Name }}-weaviate"                                                                          
    app.kubernetes.io/name: "{{ .Release.Name }}-weaviate"                                                     
    app.kubernetes.io/managed-by: helm                         
    app.kubernetes.io/component: database                       
    app.kubernetes.io/version: "{{ .Values.image.tag }}"

Note this feature will only be considered if there is end-user need for this. Please upvote this issue if this would be needed for your use case and leave a comment with your use case.

[felixthekraut]

This would be quite helpful for our internal development environments so we can run different load test instances without having to muck around with additional namespaces. Can be useful for prod as well - for example very heavy work loads can be segregated to different clusters in the same namespace.

[pommedeterresautee]

Any update ? It is a bit surprising it is still not yet supported... seems to be a design error in the chart as it s quite common and useful