Versions Compared

Old Version 8

changes.mady.by.user Felix Bauer

Saved on

compared with

New Version Current

changes.mady.by.user Hristo Grozdanov

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Let the helm chart create the volumes for you (recommended)

  1. Comment out the claimName

  2. Check the remaining settings (see table below)

  3. Run a helm install ...

  4. Now the helm chart will create 3 volumes as specified in the settings

    1. backend-uploads

    2. button3d-media

    3. button3d-private-media

  5. Setup the respective claimName to the string of the Persistent volume name. E.g.

Code Block
languageyaml
fileStorageConfig:
    uploads:
      claimName: "backend-uploads"
    media:
      claimName: "button3d-media"
    privateMedia:
      claimName: "button3d-private-media"

...

Code Block
languageyaml
fileStorageConfig:
  internal:
    enabled: true
    uploads:
      size: 1Gi
      storageClass: default
      claimName: "backend-uploads"
      accessMode: ReadWriteMany
    media:
      size: 1Gi
      storageClass: default
      claimName: "button3d-media"
      accessMode: ReadWriteMany
    privateMedia:
      size: 1Gi
      storageClass: default
      claimName: "button3d-private-media"
      accessMode: ReadWriteMany

Azure Files storage specific

Code Block
fileStorageConfig:
  internal:
    enabled: true
    # TODO: define size and name of the storage class for persistent file storage
    uploads:
      size: 1Gi
      storageClass: azurefile
      accessMode: ReadWriteMany
    media:
      size: 1Gi
      storageClass: azurefile
      accessMode: ReadWriteMany
    privateMedia:
      size: 1Gi
      storageClass: azurefile
      accessMode: ReadWriteMany

Settings Key

Possible Values

Description

enabled

true, false

Specifies if Persistent Volumes are used

size

50Gi, 200Mi, 1Ti , …

The size of the volume on initial creation. Only relevant if claimName is unset

storageClass

A supported storageClass name or default

Check https://kubernetes.io/docs/concepts/storage/storage-classes/ . You can use kubectl get storageclass to see what storage classes are supported in your cluster. Only relevant if claimName is unset

claimName

A string

See above

accessMode

ReadWriteMany or ReadWriteOnce

Specifies if you can attach to the volume from multiple pods. It is recommended to use ReadWriteMany. Only relevant if claimName is unset