helm chart now using existing pvc

[franciscouribe]

Fixed this issue https://forum.weaviate.io/t/cannot-bind-to-existing-pvc/598/2

The docs in values.yaml state:

# The Persistent Volume Claim settings for Weaviate. If there's a
# storage.fullnameOverride field set, then the default pvc will not be
# created, instead the one defined in fullnameOverride will be used

However, the current Helm Chart implementation is not using storage.fullnameOverride at all.

Now the chart is using storage.fullnameOverride when available and therefore is behaving according to the docs.

[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?

[kmichailg]

+1

Ran into this issue today. Template is not picking up the PVC I deployed prior to deploying the template.

# The Persistent Volume Claim settings for Weaviate. If there's a
# storage.fullnameOverride field set, then the default pvc will not be
# created, instead the one defined in fullnameOverride will be used
storage:
  fullnameOverride: my-pv-claim
  # size: 32Gi
  # storageClassName: ""

[antas-marcin]

@franciscouribe can you rebase your PR with the lastest master changes?