Choose an Object Storage Provider
विहंगावलोकन
इलम runs entirely on S3-compatible object storage. The bundled
helm_aio chart supports two providers natively (RustFS और
मिनियो) and integrates with any external S3 service that the cluster
can reach. Two further providers (Garage और समुद्री शैवाल एफएस) are on
the roadmap and already accommodated by the provider registry. This
page documents the trade-offs and helps an operator decide which path
to take.
Comparison matrix
The matrix compares the qualitative properties of each supported and planned provider.
| Property | RustFS | मिनियो | AWS S3 | Wasabi | Backblaze B2 | Garage (planned) | SeaweedFS (planned) |
|---|---|---|---|---|---|---|---|
| लाइसेंस | Apache-2.0 | AGPL-3.0 (server) | Proprietary (AWS) | Proprietary (Wasabi) | Proprietary (Backblaze) | Apache-2.0 / AGPL-3.0 | Apache-2.0 |
| Status in Ilum | Bundled, opt-in (planned default in 6.8.0) | Default in 6.7.x | BYO | BYO | BYO | Planned, registry-ready | Planned, registry-ready |
| Bundled chart | Yes (RustFS 0.0.99) | Yes (Bitnami 15.0.7) | नहीं | नहीं | नहीं | नहीं | नहीं |
| Distributed mode | Standalone (alpha-safe default) | Native | Managed (AWS) | Managed (Wasabi) | Managed (Backblaze) | Native (planned) | Native (planned) |
| Console UX | Embedded same-origin iframe | Embedded /बाहरी/मिनी/ proxy | Provider-hosted (no embed) | Provider-hosted (no embed) | Provider-hosted (no embed) | Planned | Planned |
| OIDC integration | Operator-supplied via extraEnv | Hydra-preconfigured | Managed by AWS IAM | Wasabi IAM | Backblaze application keys | Not yet evaluated | Not yet evaluated |
Decision tree
Three short branches cover the common deployment shapes.
"I want zero-ops bundled storage"
Use the default. मिनियो is enabled out of the box in the 6.7.x line.
helm install ilum ilum/helm_aio
To opt into RustFS (the planned default from 6.8.0) instead, enable it and disable मिनियो:
helm install ilum ilum/helm_aio \
--अस्त हो rustfs.enabled=सच्चा \
--अस्त हो minio.enabled=गलत
Either choice creates the ilum-objectstorage Service alias and wires
every bundled consumer through it.
"I already operate an S3-compatible backend"
Disable both bundled providers and point इलम at the existing service.
helm install ilum ilum/helm_aio \
--अस्त हो rustfs.enabled=गलत \
--अस्त हो minio.enabled=गलत \
--अस्त हो objectStorage.endpoint=https://s3.us-east-1.amazonaws.com
For provider-specific configuration recipes, refer to Provider Reference: External S3.
"I want to benchmark providers side by side"
Run two providers concurrently and route user traffic through the alias.
Set objectStorage.activeProvider explicitly when more than one provider
is enabled. The alias selector flips on a single helm upgrade --set.
helm install ilum ilum/helm_aio \
--अस्त हो minio.enabled=सच्चा \
--अस्त हो rustfs.enabled=सच्चा \
--अस्त हो objectStorage.activeProvider=rustfs
Reversibility
Switching providers is a single helm upgrade --set away. The
ilum-objectstorage Service alias selector flips atomically; every
bundled consumer picks up the new endpoint on its next connection.
The data side is not reversible without a migration. Refer to Migrate Between Providers for the mirror procedure that runs before the alias flip.
Constraints to be aware of
- RustFS alpha distributed mode. The bundled chart configures standalone mode. Erasure coding and multi-replica distribution are available upstream but marked "under testing".
- MinIO console pin. वही मिनियो console binds itself to the
absolute URL configured by
MINIO_BROWSER_REDIRECT_URL. The bundled default pins it to/बाहरी/मिनी/. The इलम UI's/external/object-storage/alias path redirects to that absolute URL when मिनियो is the active provider. - No simultaneous writes across providers. The cutover model assumes a single active provider at any given time. Operators that want multi-region replication should configure it at the provider layer, not by enabling two इलम providers concurrently.
Reference
- Provider reference: मिनियो · RustFS · External S3 · Garage (planned) · SeaweedFS (planned)
- Migration: Migrate Between Providers
- Troubleshooting: Troubleshoot Object Storage
- Helm values: Object Storage Helm Values