SeaweedFS: Support other filer-storages then MariaDB

[gtudan]

Name and Version

bitnami/seaweedfs 0.1.4

What architecture are you using?

amd64

What steps will reproduce the bug?

• configure the chart with mariaDB.enabled: false
• configure an alternative storage using filer.config

Are you using any custom parameters or values?

  mariadb:
    enabled: false

  filer:
    config: |
      [redis2]
      enabled = true
      address = "redis:6379"

What is the expected behavior?

It launches the filer and uses the configured persistence

What do you see instead?

It will still launch the wait-for-db as init-container that tries to connect to the mariadb.
This container should only start if mariaDb is enabled (either via the chart, or an external db)

[juan131]

Hi @gtudan

As you pointed out, this chart only supports MariaDB (or MySQL) as database for Filer (using the one installed via MariaDB sub-chart or fulfilling the externalDatabase.* parameters). Having said that, several stores could be potentially supported (MongoDB, Redis, Cassandra, PostgreSQL, Etcd, ...), see:

• https://github.com/seaweedfs/seaweedfs/wiki/Filer-Stores

We could introduce a new externalDatabase.enabled parameter (set to false by default). This way, it would be possible to set bot mariadb.enabled and externalDatabase.enabled to false and the chart, in this case, should skip the "wait-for-db" init-container & avoid setting all the WEED_MYSQL_* env vars (see https://github.com/bitnami/charts/blob/main/bitnami/seaweedfs/templates/filer/statefulset.yaml#L138-L160)

We welcome you to create a pull request with such a contribution. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.