I've noticed that MinIO has been designated as being in "maintenance mode", which means that while security fixes will still be provided, they will only be handled on a case-by-case basis. This raises a crucial question for those of us who were using MinIO for S3 compatibility in Kubernetes: What alternative solutions are you considering or have already switched to?
5 Answers
For those of you transitioning, do any of the options provide robust IAM or policy support similar to MinIO? That was one of its standout features for us.
I had a similar situation when exploring options for my large distributed storage cluster. I found that while Ceph has a steeper learning curve, it's definitely worth it if you're serious about scaling. I also experimented with GarageFS, SeaweedFS, and others but ultimately moved to Ceph using Rook, which provides great orchestration support. You'll need to invest some time in understanding it fully, but it pays off in the long run.
Just make sure you understand the system before deploying extensively. Even with its learning curve, Ceph performs really well once you get past the setup.
Garage seems to be a solid option for general use. If you're looking for something that really scales, Apache Ozone is a bit complex but definitely gets the job done. Ceph is also a reliable alternative that many have had success with.
I heard that for lightweight S3 storage, SeaweedFS might be a good fit. It's worked well for our needs, though keep in mind MinIO was my go-to for so long because of its ease of use.
Has anyone checked out RustFS? I'm curious because I've heard mixed reviews but not experienced it myself. Any thoughts?
Absolutely! Once you get the hang of the documentation and setup, it becomes much more manageable. I've also had good experiences with Ceph.