rook

Storage Orchestration for Kubernetes (by rook)

Rook Alternatives

Similar projects and alternatives to rook

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better rook alternative or higher similarity.

rook reviews and mentions

Posts with mentions or reviews of rook. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2024-01-19.
  • Ceph: A Journey to 1 TiB/s
    2 projects | news.ycombinator.com | 19 Jan 2024
    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 networking connectivity - I think that's the main thing people think of, when they think of high hardware requirements for Ceph. Ideally 10Gbe at the minimum - although more if you want higher performance - there can be a lot of network traffic, particularly with things like backfill. (25Gbps if you can find that gear cheap for homelab - 50Gbps is a technological dead-end. 100Gbps works well).

    But honestly, for a homelab, a cheap mini PC or NUC with 10Gbe will work fine, and you should get acceptable performance, and it'll be good for learning.

    You can install Ceph directly on bare-metal, or if you want to do the homelab k8s route, you can use Rook (https://rook.io/).

    Hope this helps, and good luck! Let me know if you have any other questions.

  • Running stateful workloads on Kubernetes with Rook Ceph
    4 projects | dev.to | 26 Dec 2023
    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 of a disaster.
  • Want advice on planned evolution: k3os/Longhorn --> Talos/Ceph, plus Consul and Vault
    6 projects | /r/homelab | 15 Apr 2023
    I've briefly run ceph in an external mode, you can actually use a rook deployment to manage it (sort of). Here is the documentation for doing that. For me it didn't pass my testing phase because I need better networking equipment before I can try that.
  • ATARI is still alive: Atari Partition of Fear
    2 projects | dev.to | 28 Mar 2023
    This article explains the data corruption issue happened in Rook in 2021. The root cause lies in an unexpected place and can also occurs in all Ceph environment. It's interesting that Rook had started to encounter this problem recently even though this problem has existed for a long time. It's due to a series of coincidences. I wrote this article because the word "Atari" used in a non-historical context in 2021.
  • How to Deploy and Scale Strapi on a Kubernetes Cluster 2/2
    18 projects | dev.to | 3 Feb 2023
    Rook (this is a nice article for Rook NFS)
  • Running on-premise k8s with a small team: possible or potential nightmare?
    5 projects | /r/kubernetes | 4 Jan 2023
    Storage: Favor any distributed storage you know to start with for Persistent Volumes: Ceph maybe via rook.io, Longhorn if you go rancher etc
  • My completely automated Homelab featuring Kubernetes
    10 projects | /r/homelab | 3 Jan 2023
    I've dealt with a lot of issues that are very close to just unplugging a node. Unfortunately on node lost, my stateful workloads using rook-ceph block storage won't migrate over to another node automatically due to an issue with rook. Stateless apps (ingress nginx, etc..) not using rook-ceph block failover to another node just fine. I've kind of accepted this for now and I know Longhorn has a feature that makes this work but I find rook-ceph to be more stable for my workloads.
  • [HELP] PXE Boot without data loss
    3 projects | /r/linuxadmin | 4 Dec 2022
    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.
  • SaaS Deployment Options
    4 projects | news.ycombinator.com | 12 Nov 2022
  • For those managing k8s clusters, are you using Rook + Ceph?
    2 projects | /r/devops | 1 Sep 2022
    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.
  • A note from our sponsor - LearnThisRepo.com
    learnthisrepo.com | 22 Feb 2024
    LearnThisRepo lets you learn 300+ open source repos including Postgres, Langchain, VS Code, and more by chatting with them using AI! Learn more →

Stats

Basic rook repo stats
51
11,748
9.8
6 days ago
Learn 300+ open source libraries for free using AI.
LearnThisRepo lets you learn 300+ open source repos including Postgres, Langchain, VS Code, and more by chatting with them using AI!
learnthisrepo.com