Skip to main content

SeaweedFS (Planned)

Planned, registry-ready

SeaweedFS is not yet bundled as a sub-chart of helm_aio. The provider registry under objectStorage.providers already accommodates it, so an operator can wire SeaweedFS in today through the Add a New Provider procedure. Native bundled support is on the Ilum roadmap.

Overview​

SeaweedFS is an Apache-2.0 distributed file system that exposes an S3-compatible API alongside FUSE mounts, WebDAV, and a native HDFS client. The upstream project lives at github.com/seaweedfs/seaweedfs.

PropertyValue
LicenseApache-2.0
Status in IlumPlanned (registry-ready)
Bundled chartNot yet shipped; upstream Helm chart available under k8s/charts
Bundled imageNot yet shipped
Default in helm_aioDisabled
Distributed modeNative; primary use case
Tiered storageBuilt-in hot / warm / cold tiering via volume types
Native S3 endpointServed on port 8333
Native admin UIsMaster UI on 9333, Admin UI on 23646, Filer UI on 8888
Operatorseaweedfs/seaweedfs-operator
Console UXNative admin UI; integration with the Ilum Object Storage iframe is on the roadmap
OIDC integrationNot yet evaluated against SeaweedFS

When this provider will be a good fit​

  • Workloads with mixed access patterns where hot and cold data benefit from automatic tiering.
  • Environments that also want FUSE-mounted access to the same objects alongside the S3 API.
  • Clusters with very large object counts where the upstream's volume-server design outperforms flat S3 implementations.

Provisional registry entry​

When Ilum ships bundled SeaweedFS support, the registry entry will look approximately like the snippet below. Operators wiring SeaweedFS in today through Add a New Provider can use this as a starting point.

objectStorage:
  providers:
    seaweedfs:
      enabled: true
      consolePath: /external/seaweed/
      consoleMode: nginx-rewrite

Reference​

Last updated on