The ds-operator should manage the PVC provisioning process

[wstrange]

The ds-operator creates a volume claim template on the statefulset which is used to allocate storage, possibly from a snapshot.

The template for the STS can not be changed after deployment, making it impossible to update the volume snapshot used for new instance creation.

If the operator owns and creates the PVC before a new instance is created, the statefulset controller will use that PVC in place of the volume claim template spec. The storageclass and size should be the same, but the volume snapshot source could be updated to a more recent snapshot, instead of the one used at instance template creation time.

For per instance recovery, something like velero.io may be preferable to the volume snapshot feature of the operator. Hence this issue should be considered low priority

[damonconway]

@lee-baines This ticket can be closed, but I don't have permissions.