I have some experience with Ceph, both for work, and with homelab-y stuff. First, bear in mind that Ceph is a distributed storage system - so the idea is that you will have multiple nodes. For learning, you can definitely virtualise it all on a single box - but you'll have a better time with discrete physical machines. Also, Ceph does prefer physical access to disks (similar to ZFS). And you do need decent... - Source: Hacker News / 3 months ago
Another option is to leverage a Kubernetes-native distributed storage solution such as Rook Ceph as the storage backend for stateful components running on Kubernetes. This has the benefit of simplifying application configuration while addressing business requirements for data backup and recovery such as the ability to take volume snapshots at a regular interval and perform application-level data recovery in case... - Source: dev.to / 4 months ago
This is beyond your question but might help someone else: I switch from docker-compose to kubernetes for my home lab a while ago. The storage solution I've settled on is Rook. It was a bit of up-front work learning how to get it up but now that it's done my storage is automatically managed by Ceph. I can swap out drives and Ceph basically takes care of everything itself. Source: 10 months ago
The stumbling point I am at is I want to use rook.io(Ceph) as my storage solution for the cluster. The Ceph prerequisites are one of the following:. Source: 12 months ago
Storage: Favor any distributed storage you know to start with for Persistent Volumes: Ceph maybe via rook.io, Longhorn if you go rancher etc. Source: over 1 year ago
Third, it sounds like you're building a cluster. For this you'll either want a central file server. Or better, setup a distributed storage system. For example a Ceph cluster managed by Rook. This way you can fully wipe a single node and the system will be able to recover/replicate thed data. Source: over 1 year ago
If you want build-your-own, give https://rook.io a look. Source: over 1 year ago
I just helped write a quick summary of just why you can trust your persistent workloads to Ceph, managed by Rook and it occurred to me that... I'm probably wrong. Source: over 1 year ago
Commenting on the distributed storage (cephfs) section.. We use https://rook.io/, which provides an operator to manage the nasty complexities of ceph on Kubernetes. I like it because it means I can manage the cluster lifecycle with a (not-so-simple) YAML, just like everything else :). Source: over 1 year ago
Do know that ODF has ...substantial... Resource requirements. You may want to consider using the upstream rook.io with ceph and a custom configuration. Source: almost 2 years ago
I use rook to orchestrate Ceph, so it takes care of creating the volume for the PVC etc. Unlike the sibling comment, I'm not using VMs so the virtual disk is getting mounted directly into the K8s pods. I like this because then container (in general) is immutable, and just the mutating state is stored in the volume. Source: almost 2 years ago
This is my go-to solution every time. Https://rook.io/. Source: about 2 years ago
At my work (Kubernetes Service Provider), we're running Ceph RBD and CephFS with Rook (https://rook.io) for environments which don't provide a CSI driver. However, depending on your requirements and setup, that may be vastly overkill. We did try Longhorn too, but decided on Rook.io since the admin experience is much nicer in our opinion. Source: about 2 years ago
How are you handling storage? I always thought of running this kind of setup along with something like rook.io. Source: about 2 years ago
I "nuke" the additional volumes to not contain any filesystem and then use rook.io to provide the storage for the cluster. Rook deploys ceph inside your cluster and provides the storageclasses to have block devices or even a shared filesystem. Source: about 2 years ago
I always wondered how well rook.io Ceph would perform on 8GB PI 4s and SSD USBs. Unfortunately those are very hard to buy nowadays. Source: about 2 years ago
In Kubernetes, we do storage using distributed systems. For example, Rook can be used to deploy a Ceph cluster. Source: about 2 years ago
I wonder how well rook.io performs with 8GB pis and usb SSDs. Source: over 2 years ago
Rook/longhorn for distributed storage. Source: over 2 years ago
It depends all on your environment if you're running in any cloud environment persistent storage should be a piece of cake because they do the heavy lifting. If you're in an on-prem environment something like OpenEBS or Rook might come in handy. If none of them are meeting your requirements you could also have a look at the CNCF landscape. Source: over 2 years ago
The big question is how you plan to handle data storage. You'll need a robust storage solution in order to manage all your data. Something like Rook can be used as the basis for a storage platform. Source: almost 3 years ago
Do you know an article comparing ROOK to other products?
Suggest a link to a post with product alternatives.
This is an informative page about ROOK. You can review and discuss the product here. The primary details have not been verified within the last quarter, and they might be outdated. If you think we are missing something, please use the means on this page to comment or suggest changes. All reviews and comments are highly encouranged and appreciated as they help everyone in the community to make an informed choice. Please always be kind and objective when evaluating a product and sharing your opinion.