openskills.info
Rook logoCourse Preview

Rook

Rook is a Kubernetes operator that deploys and manages Ceph storage. It turns Kubernetes resources into block, shared-file, and object storage services while Ceph stores and protects the data.

itCloud native tools and technologies

Don't Panic — Rook

Rook is the Kubernetes operator that gets Ceph storage assembled, configured, and kept pointed at the declaration. It is not a magic storage box hiding behind an agreeable bird name. Ceph still stores and protects the bytes. Rook turns Kubernetes custom resources into the arrangements Ceph needs, which is considerably more useful than collecting YAML for its own sake.

The important split is between the control path and the data path. A CephCluster is the declaration that starts the control path: Rook watches it, creates and manages Ceph components, and reports status back through Kubernetes. An application does not send its data through the operator. For volumes it uses CSI; for buckets it reaches the RADOS Gateway. The operator is the foreman, not the delivery van.

Ceph then presents three different storage contracts. RBD is a disk-like block volume reached from a claim and storage class. CephFS is a shared file-system namespace for applications that need paths and files. RGW is the object gateway for buckets and objects through an S3-compatible endpoint. One cluster can provide all three, which is convenient until somebody assumes that a bucket is a folder wearing a hat. It is not.

The surprising part is that reconciliation cannot improve the hardware plan. It cannot invent another disk, make two replicas on one host independent, supply spare recovery capacity, or turn replication into a backup. Rook can arrange the declared system repeatedly; Ceph can protect the current state through selected failures; neither can recover a history that nobody preserved independently.

Start with the Intro for the full control and data-path map. The Slides compress the three contracts and the two health layers into a visual route. The Cheatsheet is for tracing a failed claim, mount, or endpoint from Kubernetes evidence to Ceph evidence. Read the Reference tab when a real cluster is next on the agenda, especially before selecting devices or performing an upgrade. That is when the pleasant diagram meets the less optional reality of storage.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources