Ease the process to add extra volumes for local data registration about substra-backend HOT 2 CLOSED

Hello @ClementGautier,

Since the release 1.8.0 of the substra-backend chart it is not necessary anymore to copy the whole persistence.volumes object.
For example if in your values you define only something like this:

persistence:
  volumes:
    customVolume:
      size: "2Gi"
      readOnly:
        server: false
        worker: true

you will have a new volume mounted on your backend and worker pod under the /var/substra/medias/ path.
Result in the rendered yaml:

containers:
      - name: substra-backend        
        volumeMounts:
          - name: data-customVolume
            mountPath: /var/substra/medias/customVolume
            readOnly: false

tied to the following pvc:

      - name: data-customVolume
        persistentVolumeClaim:
          claimName: RELEASE-NAME-substra-backend-customVolume

but all the required pvc's (compositealgos, computeplan, ...) will still be present alongside this new one.

For the point number two they are not hardcoded to be able to specify volume sizes independently which can be useful sometimes, but as stated above you do not need to redefine the wole list of volumes anymore. This is a benefit from the transition we made from a yaml list to a yaml object.

from substra-backend.

Great! That fixes the issue then :)

from substra-backend.