Handle multiple storage classes in Helm chart

[gpothier]

Describe the feature you'd like to have

The Helm chart currently supports the creation of one StorageClass. I think it could be useful to allow the creation of multiple storage classes, given that the chart already supports the configuration of various clusters (through the array in csiConfig).

Eg. instead of:

storageClass:
  # Specifies whether the Storage class should be created
  create: true
  name: mysc
  clusterID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  fsName: myfs

we could have:

storageClasses: {}

if no StorageClass should be created, or:

storageClasses:
  mysc:
    clusterID: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
    fsName: myfs
  myothersc:
    clusterID: xxxxxxxx-xxxx-xxxx-xxxx-yyyyyyyyyyyy
    fsName: myotherfs

(I am partial to using maps instead of arrays as it makes it easier to add different items by providing multiple values files which are then merged).

What is the value to the end user? (why is it a priority?)

In my particular use case, I need a storage class for volumes that contain important data that needs to be included in backups, and another one for volumes that contain temporary data, or data that does not need to be backed up.

How will we know we have a good solution? (acceptance criteria)

The feature should work correctly and be clearly documented

[mustdiechik]

you can do it via extraDeploy (Secret + StorageClass )

[gpothier]

Yes, but that would be quite a lot of lines for each extra StorageClass, instead of just two lines, and we would have one SC defined in one way, and the rest defined in a completely different way.