ROOK Reviews and Details

Social recommendations and mentions

• Garage – An S3 object store so reliable you can run it outside datacenters

  Copy/paste from a previous thread [0]: We’ve done some fairly extensive testing internally recently and found that Garage is somewhat easier to deploy, but is not as performant at high speeds. IIRC we could push about 5 gigabits of (not small) GET requests out of it, but something blocked it from reaching the 20-25 gigabits (on a 25g NIC) that MinIO could reach (also 50k STAT requests/s) I don’t begrudge it that.... - Source: Hacker News / 8 months ago

• Kubernetes homelab - Learning by doing, Part 4: Storage

  Distributed storage systems enable us to store data that can be made available clusterwide. Excellent! But dynamically apportioning storage across a multi-node cluster is a very complex job. So this is another area where Kubernetes typically outsources the job to plugins (e.g. Cloud providers like Azure or AWS, or systems like Rook or Longhorn). - Source: dev.to / over 2 years ago

• Data on Kubernetes: Part 2 - Deploying Databases in K8s with PostgreSQL, CloudNative-PG, and Ceph Rook on Amazon EKS

  In this blog post, we'll explore how to combine CloudNative-PG (a PostgreSQL operator) and Ceph Rook (a storage orchestrator) to create a PostgreSQL cluster that scales easily, recovers from failures, and ensures data persistence - all within an Amazon Elastic Kubernetes Service EKS cluster. - Source: dev.to / about 2 years ago

• Searchable Kubernetes StorageClass Listing

  My experience is that OpenEBS and Longhorn are cool and new and simplified, but that I would only trust my life to Rook/Ceph. If it's going into production, I'd say look at https://rook.io/ - Ceph can do both block and filesystem volumes. - Source: Hacker News / about 2 years ago

• Ceph: A Journey to 1 TiB/s

  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 / over 2 years ago

• Running stateful workloads on Kubernetes with Rook Ceph

  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 / over 2 years ago

• People who run Nextcloud in Docker: Where do you store your data/files? In a Docker volume, or on a remote server/NAS?

  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: about 3 years ago

• Rook/Ceph with VM nodes on research cluster?

  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: about 3 years ago

• Running on-premise k8s with a small team: possible or potential nightmare?

  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 3 years ago

• [HELP] PXE Boot without data loss

  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 3 years ago

• Storage solutions (open-source)

  If you want build-your-own, give https://rook.io a look. Source: over 3 years ago

• For those managing k8s clusters, are you using Rook + Ceph?

  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: almost 4 years ago

• Self Hosted Kubernetes - Solving the Storage Problem

  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: almost 4 years ago

• Distributed storage

  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: about 4 years ago

• Anybody here shooting for high availability in their home lab?

  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: about 4 years ago

• Storage provisioner for self-created clusters in 2022, for disk-heavy workload like MySQL?

  This is my go-to solution every time. Https://rook.io/. Source: over 4 years ago

• Recommended on-premis PVC dynamic provider

  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: over 4 years ago

• Scaling down in size/electricity cost/noise, still packing a punch 18c/36t@3.8GHz, 192GB RAM

  How are you handling storage? I always thought of running this kind of setup along with something like rook.io. Source: over 4 years ago

• Installing a small kubernetes cluster on cloud VMs

  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: over 4 years ago

• Personal K8s cluster

  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: over 4 years ago

• Is there a HA memory solution?

  In Kubernetes, we do storage using distributed systems. For example, Rook can be used to deploy a Ceph cluster. Source: over 4 years ago