Technology

Rook

A Kubernetes storage orchestrator that deploys and manages Ceph clusters on Kubernetes, providing K8s-native S3-compatible object storage via Ceph's RADOS Gateway.

6 connections 3 resources

Summary

What it is

A Kubernetes storage orchestrator that deploys and manages Ceph clusters on Kubernetes, providing K8s-native S3-compatible object storage via Ceph's RADOS Gateway.

Where it fits

Rook bridges the gap between Kubernetes-native operations and enterprise storage. It automates the deployment, scaling, and lifecycle management of Ceph on K8s — enabling platform teams to offer self-service S3-compatible storage to application developers.

Misconceptions / Traps
  • Rook is not a storage system itself. It is an operator that manages Ceph on Kubernetes. Operational complexity is still Ceph's complexity — Rook automates deployment, not troubleshooting.
  • Running Ceph on Kubernetes adds a layer of abstraction that can complicate debugging. Storage issues may manifest as pod failures, PVC errors, or OSD crashes.
Key Connections
  • depends_on Ceph — orchestrates Ceph clusters
  • implements S3 API — via Ceph RADOS Gateway
  • scoped_to Kubernetes Object Provisioning & Policy — K8s-native storage management
  • solves Vendor Lock-In — self-hosted S3-compatible on Kubernetes

Definition

What it is

A Kubernetes storage orchestrator that deploys and manages Ceph (including its S3-compatible RADOS Gateway) as a native Kubernetes resource using operators and CRDs.

Why it exists

Running Ceph for S3-compatible storage requires significant operational expertise. Rook automates Ceph deployment, scaling, and healing on Kubernetes, making self-hosted S3-compatible storage a declarative, GitOps-managed resource.

Primary use cases

Kubernetes-native S3-compatible storage, automated Ceph management, cloud-native on-premise object storage.

Connections 6

Outbound 6

Resources 3