...
Let the helm chart create the volumes for you (recommended)
Comment out the
claimNameCheck the remaining settings (see table below)
Run a
helm install ...Now the helm chart will create 3 volumes as specified in the settings
backend-uploadsbutton3d-mediabutton3d-private-media
Setup the respective
claimNameto the string of the Persistent volume name. E.g.
| Code Block | ||
|---|---|---|
| ||
fileStorageConfig:
uploads:
claimName: "backend-uploads"
media:
claimName: "button3d-media"
privateMedia:
claimName: "button3d-private-media" |
...
| Code Block | ||
|---|---|---|
| ||
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"
# fileStorageConfig.internal.privateMedia.claimName -- Use an existing PVC to persist data. If unspecified, a claim will be created with the name "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 |
|---|---|---|
|
| Specifies if Persistent Volumes are used |
|
| The size of the volume on initial creation. Only relevant if |
| A supported storageClass name or | Check https://kubernetes.io/docs/concepts/storage/storage-classes/ . You can use |
| A string | See above |
|
| Specifies if you can attach to the volume from multiple pods. It is recommended to use |