Rook-Ceph

Rook-Ceph is a cloud-native storage orchestrator that deploys and manages Ceph on Kubernetes, providing native file, block, and object storage for homelab and…

  • Cloud
  • Infrastructure
  • Tools & Utilities
Rook-Ceph is a cloud-native storage orchestrator that deploys and manages Ceph on Kubernetes, providing native file, block, and object storage for homelab and production cluster workloads.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

72/100 Good

Maintained
100last commit 1 day ago
Popular
8313,714 GitHub stars
Easy to install
251 install platform, install notes
Light to run
108 GB minimum RAM
Security check
93no serious findings, 1 minor, CI, tests, OpenSSF Scorecard 9.1/10

Availability: platform listings confirmed today

GitHub stars
13,714
Open issues
131
Last commit
2026-11-20
Latest release
v1.21.2
License
Apache-2.0
Activity
rising

Checked today - source: GitHub (rook/rook)

Resources & Compatibility

Minimum requirements: 8 GB RAM.

Checked 40 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install LVM on Ubuntu storage nodes Install LVM (the package that manages disk volumes) on every Ubuntu node that will run Ceph OSDs. Without it, OSD pods can fail to start after a node reboot. source
  • Check Rook pods after installing Run kubectl get pod -n rook-ceph after the install to confirm the cluster components are running. Pods that crash or stay pending often point to a missing prerequisite or configuration mistake. source
  • Replace object storage example keys If you are using object storage, replace the example access key and secret key with the real credentials before connecting an app. Placeholder or wrong keys make S3-style connections fail. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What should I do if Ceph daemons need the local configuration and data path fixed?

Set dataDirHostPath to a path on the local host such as /var/lib/rook, reapply the Cluster CRD, and restart the MON, MGR, OSD, and RGW daemons.

Does Rook-Ceph work well when Kubernetes and Ceph nodes are separate?

A homelab discussion reports that Rook works well with Kubernetes when the Kubernetes and Ceph nodes are separate and connected by a fast network.

Do I need clustered storage to use Rook-Ceph?

A Reddit commenter says you may find you don't need clustered storage or don't want to add the number of nodes Ceph needs to flourish.

How do I report a potential Rook security vulnerability?

Email [email protected]. The team will send a confirmation and follow up when the report has been identified positively or negatively.

What should I prepare when troubleshooting a Rook cluster?

The documentation points to tips on what information helps solve the issues you might be seeing. If those suggestions do not resolve the problem, the Rook team can help troubleshoot.

Answers sourced from github.com, github.com, rook.io, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads