Rook-ceph-cluster

A Helm chart that installs the Rook operator and deploys a single Ceph cluster, giving your Kubernetes cluster distributed file, block, and object storage…

  • Cloud
  • Infrastructure
  • Tools & Utilities
A Helm chart that installs the Rook operator and deploys a single Ceph cluster, giving your Kubernetes cluster distributed file, block, and object storage without managing Ceph manually.

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.

77/100 Good

Maintained
100last commit 14 days ago
Popular
8313,704 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
13,704
Open issues
145
Last commit
2026-11-06
Latest release
v1.21.2
License
Apache-2.0
Activity
steady

Checked 14 days ago - source: GitHub (rook/rook)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Install LVM on storage nodes Install LVM (a Linux tool for managing disk storage) on every node that will hold Ceph data disks, for example with sudo apt-get install -y lvm2 on Ubuntu. Without it, Ceph OSD pods that store your data may fail to start after a reboot. source
  • Test block storage with sample apps Run kubectl create -f mysql.yaml and kubectl create -f wordpress.yaml from the deploy/examples folder to verify Rook can create and mount block storage volumes. If you want to click into WordPress, open TCP port 30841 on a Kubernetes node; otherwise you cannot reach the app in a browser. source
  • Replace object storage keys If you use the S3-compatible object store (Amazon-style bucket storage), set AWS_HOST, PORT, AWS_ACCESS_KEY_ID, and AWS_SECRET_ACCESS_KEY to your real Rook service address and credentials. Without the correct host, port, and keys, S3-style clients will be refused and cannot read or write buckets. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What setup caution is mentioned for a Rook Ceph quickstart deployment?

Avoid relying only on the quickstart example if you want a robust deployment. The thread describes Rook as an easy Ceph operator when configured beyond that minimal example.

How can I cleanly shut down a small Rook Ceph homelab cluster?

The source points to a homelab thread about a cluster with Raspberry Pi Kubernetes masters and Dell Optiplex worker nodes. It is useful for troubleshooting the shutdown sequence on that mixed small hardware setup.

How can I deploy Rook Ceph in KinD without repeated setup problems?

A shared tutorial covers getting Rook Ceph working in a KinD cluster on an M1 MacBook Pro. It points to a written example and linked resources to avoid repeated cluster setup problems.

Where should I start when investigating a Rook Ceph cluster issue?

Kubernetes status and logs are the main resources needed to investigate issues in any Rook cluster. Kubernetes status is the first line of investigation.

Answers sourced from discuss.kubernetes.io, rook.io, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads