3 ms·
I'd throw minio [1] in the list there as well for homelab k8s object storage. [1] https://min.io/ https://min.io/
by reactordev 3y ago
I'd throw minio [1] in the list there as well for homelab k8s object storage.
[1] https://min.io/ https://min.io/
- speedgoose 3y agoAlso garage. https://garagehq.deuxfleurs.fr/ https://garagehq.deuxfleurs.fr/
- BlackLotus89 3y agoGarage seems to only to duplication https://garagehq.deuxfleurs.fr/documentation/design/goals/ https://garagehq.deuxfleurs.fr/documentation/design/goals/ > Storage optimizations: erasure coding or any other coding technique both increase the difficulty of placing data and synchronizing; we limit ourselves to duplication. This is probably a nogo for most use cases where you work with large datasets....
- speedgoose 3y agoYes I mentioned it in the context of homelabs, it’s not an alternative to Ceph or MinIO for large installations. But the simplicity is appreciated. You can recover all the data using rsync.
- plagiarist 3y agoMinio doesn't make any sense to me in a homelab. Unless I'm reading it wrong it sounds like a giant pain to add more capacity while it is already in use. There's basically no situation where I'm more likely to add capacity over time than a homelab.
- reactordev 3y agoYou get a new nas (minio server pool) and you plug it into your home lab (site replication) and now it's part of the distributed minio storage layer (k8s are happy). How is that hard? It's the same basic thing for Ceph or any distributed JBOD mass storage engine. Minio has some funkiness with how you add more storage but it's totally capable of doing it while in use. Everything is atomic.