Building Blocks: Raw Block PVs in Rook-Ceph
summary
Rook-Ceph uses raw block PVs so Ceph OSDs run on PVC-backed block devices that can move between nodes; the operator creates PVCs from a storage class device set and tracks OSD identity by PVC name. Demo deletes a node and detached GP2 volumes reattach and OSDs come up on other nodes with no data loss. Workarounds include an init container copying the block device into an emptyDir to bypass privileged /dev mounts and passing explicit LV names to avoid LVM confusion; recommend spread across AZs.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:45Introductions
- 2:16Storage Resource Types
- 4:18Dynamic Provisioning
- 6:48VolumeMode: File vs Block
- 8:37VolumeMode: Block
- 9:49VolumeMode vs. Access Mode
- 11:14What is Rook?
- 11:34Rook Operators
- 13:03Rook-Ceph
- 15:11Local Storage OSDs
- 17:41Storage ClassDevice Sets
- 23:11Check Your Privilege
- 24:20Virtually Lost
- 25:05Proper Distribution
related talks
34mBuilding Blocks: How Raw Block PVs Changed the Way We Look at Storage
27mRook: Intro and Ceph Deep Dive
35mBest Practices of Production-Grade Rook/Ceph Cluster
30mWhatever Can Go Wrong, Will Go Wrong – Rook/Ceph and Storage Failures
41mRook - Running Ceph Using Kubernetes
31mRook: Intro and Deep Dive With Ceph Storage
35mDistributed storage with Rook
29mSimplifying Storage in Kubernetes with Rook-Ceph