Support multiple deployments in the same namespace

[delamainer]

Support multiple deployments in the same namespace.

Issue: #115

This feature is requested by multiple users.

[delamainer]

@antas-marcin Hi, please review this pull request.

[weaviate-git-bot]

To avoid any confusion in the future about your contribution to Weaviate, we work with a Contributor License Agreement. If you agree, you can simply add a comment to this PR that you agree with the CLA so that we can merge.

beep boop - the Weaviate bot 👋🤖

PS:
Are you already a member of the Weaviate Slack channel?

[delamainer]

I agree with the CLA.

[delamainer]

@antas-marcin Is there any chance that this feature will be adopted?

[antas-marcin]

@delamainer I will try to find time to look into your PR this week, sorry for the delay on this.

[kfkonrad]

@delamainer please consider rebasing and fixing conflicts
@antas-marcin please consider reviewing this PR once the conflicts are fixed

[bender316]

Any chance this PR might come back to live!? While integration weaviate into our umbrella chart I came across the same issue.

I would advice against using .Release.Name as the name prefix. This woul mean that you can have only one weaviate instance per release. Maybe there is never a situation where this is needed but defining a name template for it like the Bitnami charts are doing it (see [1] and [2]) would be better.

[1] https://github.com/bitnami/charts/blob/main/bitnami/postgresql/templates/primary/statefulset.yaml#L10
[2] https://github.com/bitnami/charts/blob/main/bitnami/postgresql/templates/_helpers.tpl#L20