NB: the example file (helm/examples/local/values-localfile.yaml) is just that an example.
It assumes (there is a comment in the local/README) that the chart was installed with helm install localfile,
but you can install with any name, if you capture the output and use that instead of the example.

That's exactly what I had to do.  Thank you for that!

>values-localfile.yaml sets the dalistorage pvc to dali-hpcc-localfile-pvc.

ok they are wrong, I will correct them.

However the recommended way to install is to capture the output from the hpcc-localfile (or other similar charts), and use that directly.
That way you can have you own hpcc-localfile values file, that for example adds your own planes/specs. and use the hpcc-localfile , without relying on the static (out of sync) values-localfile.yaml

So to clarify, values-localfile.yaml sets the dalistorage pvc to dali-hpcc-localfile-pvc.  However, when I go to install the cluster, dali won't actually start.  If I run kubectl describe pod [dalipod] mydali, it'll tell me that it's expecting the dalistorage pvc to be this instead: dali-localfile-hpcc-localfile-pvc  (I'm not exactly sure why this is the case and  was rather surprised by this as well)

Instead of installing mycluster with values-localfile.yaml, I had to override it with my own yaml that looks like this:

storage:
planes:

• name: dali
  pvc: dali-localfile-hpcc-localfile-pvc
  prefix: "/var/lib/HPCCSystems/dalistorage"
  category: dali

• name: dll
  pvc: dll-localfile-hpcc-localfile-pvc
  prefix: "/var/lib/HPCCSystems/queries"
  category: dll

• name: sasha
  pvc: sasha-localfile-hpcc-localfile-pvc
  prefix: "/var/lib/HPCCSystems/sasha"
  category: sasha

• name: data
  pvc: data-localfile-hpcc-localfile-pvc
  prefix: "/var/lib/HPCCSystems/hpcc-data"
  category: data

• name: mydropzone
  pvc: mydropzone-localfile-hpcc-localfile-pvc
  prefix: "/var/lib/HPCCSystems/dropzone"
  category: lz

sasha:
wu-archiver:
plane: sasha
dfuwu-archiver:
plane: sasha