Replace Wasabi with our own object storage

[kelson42]

We more and more use object-storage backend to store our "blobs". Since years this service is provided by PaaS provider Wasabi.

Wasabi is not a bad product at all and it offer many nice features:

• Cost effective
• fine graded access control
• DC all over the world
• No egress costs

But we still suffer of the few problems:

• Costs increasing over time (we use it more), currently around 300 USD/month
• Slow download/upload speeds
• No green computing
• No fine grained control of storage consumption (month granularity)
• US based company
• Not super stable

At this stage, I believe it would make sense to assess the possibility of having our own server with Minio to fix all or part of the problems we face.

[siddheshwar-9897]

Hi sir
I’ve gone through Issue #399 about replacing Wasabi with MinIO, and I understand the motivation — reducing costs, improving speed, and gaining more control over storage infrastructure.

I’ve started exploring MinIO locally and looked into its advantages like:

S3 compatibility (so integration could be smooth)

Full control over storage usage

Better performance on self-hosted environments

Easier debugging and monitoring

[siddheshwar-9897]

I’m ready to start contributing toward the migration. Could you guide me on:
Where in the codebase Wasabi is currently being used or configured?
Are we aiming to fully replace Wasabi or start with a mirror/minimal backup use case first?
should I work on integrating MinIO into an existing K8s cluster or mock it locally first?

[benoit74]

@siddheshwar-9897 no offense, but this issue is far beyond what an external contributor can do since you need access to our infrastructure. And issue is not ready all to be implemented, many questions are still open

[siddheshwar-9897]

Hi, thanks for the feedback — I totally understand the concern about infrastructure access. That said, I’d still love to work on this issue, at least on the groundwork part.

I’ve already:

Analyzed all .cm.yaml files referencing Wasabi

Set up MinIO locally using WSL to mimic the S3 environment

Verified that MinIO could replace Wasabi in local dev/testing setups

[siddheshwar-9897]

I’d be happy to:

Prepare a PoC (proof of concept) for replacing Wasabi URLs with MinIO URLs in the .cm.yaml config files

Write docs or scripts that could help with migrating/test environments

Collaborate with a core member for production-specific changes if needed