This operator vs. the upstream Helm chart

[dhess]

Hi, we're considering doing a Seaweed FS deployment in our Kubernetes cluster. We plan to have at least 2 different classes of storage as backing stores — traditional high-density, low-performance spinning hard drives; and high-performance SSDs — which we don't want to mix. Our plan is to have 2 different "tenants": one for the HDD storage, and one for the SSD storage. Applications will be configured to use one or the other tenant depending on their storage needs.

For our use case, can someone more familiar with Seaweed FS explain what is the advantage of using this operator vs the upstream project's Helm chart? Does the operator make it easier to install multiple tenants? (I assume that with the upstream Helm chart, we would just install it twice, in different namespaces, one for each tenant/class of storage.)