I just reviewed #160, so I started puzzling over if we could also have the chart add the actual persistentVolumeClaims. But, once I read all the discussions in there, I think including the PVCs in the stackstorm-ha chart has some gotchas.

Quoting #160 (comment):

Is it possible for you to use StatefulSet with persistentVolumeTemplate instead?
Using what you've suggested deletes pvc when chart is deleted.
I tried using

annotations:
  helm.sh/resource-policy: keep

& it works fine until we reinstall the chart which fails with:

release stackstorm failed: persistentvolumeclaims "st2-packs-pvol-stackstorm" already exists

Or is there any way we can resuse PV with dynamic provisioning.

Maybe this is another reason to keep the PVC or other storage definition and management separate from the StackStorm chart. I wouldn't want any kind of helm maintenance (install, upgrade, delete, reinstall) to touch that storage, at least in the cluster I'm working on.

Right now I'm preparing to upgrade from a modified 1ppc installation, switching over to the stackstorm-ha chart. I will be reusing mongo, rabbitmq, redis, and my rook-ceph (via flexVolume) installations. So, I'll only be replacing the StackStorm deployments, services (plus migrating some configMaps and secrets to the stackstorm-ha format). I'm trying very hard to make this upgrade as seamless as possible.

That said, I'd be okay if others wanted the chart to optionally also create persistentVolumeClaims, even though I don't need or want them. Any thoughts?