Ceph turns storage spread across several machines into a shared storage system. Applications can use it as virtual disks, shared filesystems or an object store accessed through an API. It is useful when a platform needs those storage services under its own control rather than relying only on individual machine disks. Running Ceph also means operating the servers, disks, replication and recovery that keep the stored data available.
Deployment and operating notes
The recovered link points to ceph/ceph-helm, whose README still describes the former central Helm stable repository. Current Rook documentation provides an operator, Ceph cluster resources and CSI integration for Kubernetes. This is not a statement that an old Ceph cluster can be adopted by installing Rook over its existing pods or disks.
First identify whether Ceph runs inside Kubernetes or is an external storage system consumed by Kubernetes clients. Inventory monitors, OSD devices, cluster identity, keys, pools, CRUSH placement and filesystem or object-store users. A storage migration must protect the data plane and the control-plane metadata; retaining PVC objects alone is insufficient. Follow a documented operator or external-cluster path for the selected Ceph and Rook versions. Rehearse recovery and application I/O before changing provisioners, reclaim policies or storage classes. Avoid wiping or preparing disks as part of a chart trial on an existing cluster. Replication improves availability but does not replace independent recovery copies.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub does not mark ceph/ceph-helm archived or disabled; this does not establish active maintenance, support or compatibility. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Original publication: 2018-09-22T07:55:50+00:00. Preserved for context. Commands, versions, prices and results below reflect the original research.
Ceph is designed to provide highly scalable object, block and file based storage under a unified system.
Storage clusters are designed to run on commodity hardware, using an algorithm called CRUSH (Controlled Replication Under Scalable Hashing) to ensure data is evenly distributed across the cluster and that all cluster nodes can retrieve data quickly without any centralized bottlenecks.
Object storage is accessible through Amazon Simple Storage Service (S3) and OpenStack Swift REST based application programming interfaces (APIs), and a native API for integration with software applications.
Block storage makes use of a Ceph Block Device, which is a virtual disk that can be attached to bare-metal Linux-based servers or virtual machines. The Ceph Reliable Autonomic Distributed Object Store (RADOS) provides block storage capabilities, such as snapshots and replication. The Ceph RADOS Block Device is integrated to work as a back end with OpenStack Block Storage.
Ceph file storage makes use of the Portable Operating System Interface (POSIX)-compliant Ceph file system (CephFS) to store data in a Ceph Storage Cluster. CephFS uses the same clustered system as Ceph block storage and Ceph object storage.
The post Ceph appeared first on kubedex.com.
Sources & further reading
Spotted something that needs another look?
Help improve this page →