Persisence-related chart values not being respected about node-red-chart HOT 2 OPEN

Hey @rossigee,

Can you elaborate more on the issue and why you had to use the workaround you went?

from node-red-chart.

Never mind. I don't think this is a bug, just a documentation issue that sent me off on a tangent.

The values.yaml (without comments) suggests we configure persistence using values in the chart like this:

persistence:
  enabled: false
  # storageClass: "-"
  # existingClaim: your-claim
  accessMode: ReadWriteOnce
  size: 5Gi
  keepPVC: false

However, the template file for the deployment contains an undocumented subPath attribute which led me to think the docs were out-of-sync. Also I notice it mounts the /data volume regardless of the value of enabled or not, which prevents us using the extraVolumes if we needed more customisation than just subPath.

Anyway, it took me a while to figure it out how it worked but I got there in the end. Perhaps adding a brief 'Storage' section to the README would be useful for others?

In the end what I was trying to do was easily achieved using this:

    persistence:
      enabled: true
      existingClaim: nodered-data

from node-red-chart.