Documentation/ceph-storage.md

---
title: Ceph Storage
weight: 2000
---

# Ceph Storage

Ceph is a highly scalable distributed storage solution for **block storage**, **object storage**, and **shared filesystems** with years of production deployments.

## Design

Rook enables Ceph storage to run on Kubernetes using Kubernetes primitives.
With Ceph running in the Kubernetes cluster, Kubernetes applications can
mount block devices and filesystems managed by Rook, or can use the S3/Swift API for object storage. The Rook operator
automates configuration of storage components and monitors the cluster to ensure the storage remains available
and healthy.

The Rook operator is a simple container that has all that is needed to bootstrap
and monitor the storage cluster. The operator will start and monitor [Ceph monitor pods](ceph-mon-health.md), the Ceph OSD daemons to provide RADOS storage, as well as start and manage other Ceph daemons. The operator manages CRDs for pools, object stores (S3/Swift), and filesystems by initializing the pods and other resources necessary to run the services.

The operator will monitor the storage daemons to ensure the cluster is healthy. Ceph mons will be started or failed over when necessary, and
other adjustments are made as the cluster grows or shrinks.  The operator will also watch for desired state changes
specified in the Ceph custom resources (CRs) and apply the changes.

Rook automatically configures the Ceph-CSI driver to mount the storage to your pods.

![Rook Components on Kubernetes](media/kubernetes.png)

The `rook/ceph` image includes all necessary tools to manage the cluster. Rook is not in the Ceph data path.
Many of the Ceph concepts like placement groups and crush maps
are hidden so you don't have to worry about them. Instead Rook creates a simplified user experience for admins that is in terms
of physical resources, pools, volumes, filesystems, and buckets. At the same time, advanced configuration can be applied when needed with the Ceph tools.

Rook is implemented in golang. Ceph is implemented in C++ where the data path is highly optimized. We believe
this combination offers the best of both worlds.
top level doc reorg 2018-11-20 10:12:21 -08:00			`---`
docs: table of contents with a storage provider organization 2018-12-08 08:07:03 -07:00			`title: Ceph Storage`
add 00 to all the weights in *.md files 2019-02-04 09:46:00 -08:00			`weight: 2000`
top level doc reorg 2018-11-20 10:12:21 -08:00			`---`

docs: table of contents with a storage provider organization 2018-12-08 08:07:03 -07:00			`# Ceph Storage`
top level doc reorg 2018-11-20 10:12:21 -08:00
ceph: docs: unified formatting and style 2019-10-24 10:22:08 +02:00			`Ceph is a highly scalable distributed storage solution for block storage, object storage, and shared filesystems with years of production deployments.`
top level doc reorg 2018-11-20 10:12:21 -08:00
			`## Design`

docs: refactor documentation for ceph provider 2021-09-10 16:56:55 -06:00			`Rook enables Ceph storage to run on Kubernetes using Kubernetes primitives.`
enable the ceph-csi driver by default 2019-08-01 16:31:50 -06:00			`With Ceph running in the Kubernetes cluster, Kubernetes applications can`
top level doc reorg 2018-11-20 10:12:21 -08:00			`mount block devices and filesystems managed by Rook, or can use the S3/Swift API for object storage. The Rook operator`
			`automates configuration of storage components and monitors the cluster to ensure the storage remains available`
			`and healthy.`

			`The Rook operator is a simple container that has all that is needed to bootstrap`
docs: refactor documentation for ceph provider 2021-09-10 16:56:55 -06:00			`and monitor the storage cluster. The operator will start and monitor [Ceph monitor pods](ceph-mon-health.md), the Ceph OSD daemons to provide RADOS storage, as well as start and manage other Ceph daemons. The operator manages CRDs for pools, object stores (S3/Swift), and filesystems by initializing the pods and other resources necessary to run the services.`
top level doc reorg 2018-11-20 10:12:21 -08:00
			`The operator will monitor the storage daemons to ensure the cluster is healthy. Ceph mons will be started or failed over when necessary, and`
			`other adjustments are made as the cluster grows or shrinks. The operator will also watch for desired state changes`
docs: refactor documentation for ceph provider 2021-09-10 16:56:55 -06:00			`specified in the Ceph custom resources (CRs) and apply the changes.`
top level doc reorg 2018-11-20 10:12:21 -08:00
docs: refactor documentation for ceph provider 2021-09-10 16:56:55 -06:00			`Rook automatically configures the Ceph-CSI driver to mount the storage to your pods.`
top level doc reorg 2018-11-20 10:12:21 -08:00
			`![Rook Components on Kubernetes](media/kubernetes.png)`

docs: refactor documentation for ceph provider 2021-09-10 16:56:55 -06:00			The `rook/ceph` image includes all necessary tools to manage the cluster. Rook is not in the Ceph data path.
			`Many of the Ceph concepts like placement groups and crush maps`
			`are hidden so you don't have to worry about them. Instead Rook creates a simplified user experience for admins that is in terms`
top level doc reorg 2018-11-20 10:12:21 -08:00			`of physical resources, pools, volumes, filesystems, and buckets. At the same time, advanced configuration can be applied when needed with the Ceph tools.`

			`Rook is implemented in golang. Ceph is implemented in C++ where the data path is highly optimized. We believe`
			`this combination offers the best of both worlds.`