This repo contains the Ceph Container Storage Interface (CSI) driver for RBD, CephFS and Kubernetes sidecar deployment YAMLs to support CSI functionality: provisioner, attacher, resizer, driver-registrar and snapshotter.
Ceph CSI plugins implement an interface between a CSI-enabled Container Orchestrator (CO) and Ceph clusters. They enable dynamically provisioning Ceph volumes and attaching them to workloads.
Independent CSI plugins are provided to support RBD and CephFS backed volumes,
examples/
.NOTE:
Arm64
support is experimental.Status: GA
Ceph CSI drivers are currently developed and tested exclusively in Kubernetes environments.
Ceph CSI Version | Container Orchestrator Name | Version Tested |
---|---|---|
v3.12.0 | Kubernetes | v1.29, v1.30, v1.31 |
v3.11.0 | Kubernetes | v1.26, v1.27, v1.28, v1.29 |
There is work in progress to make this CO-independent and thus support other orchestration environments (Nomad, Mesos..etc).
NOTE:
The supported window of Ceph CSI versions is "N.(x-1)": (N (Latest major release) . (x (Latest minor release) - 1)).
For example, if the Ceph CSI latest major version is 3.9.0
today, support is
provided for the versions above 3.8.0
. If users are running an unsupported
Ceph CSI version, they will be asked to upgrade when requesting support.
Please refer rbd nbd mounter for its support details.
Plugin | Features | Feature Status | CSI Driver Version | CSI Spec Version | Ceph Cluster Version | Kubernetes Version |
---|---|---|---|---|---|---|
RBD | Dynamically provision, de-provision Block mode RWO volume | GA | >= v1.0.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.14.0 |
Dynamically provision, de-provision Block mode RWX volume | GA | >= v1.0.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.14.0 | |
Dynamically provision, de-provision Block mode RWOP volume | Alpha | >= v3.5.0 | >= v1.5.0 | Pacific (>=v16.2.0) | >= v1.22.0 | |
Dynamically provision, de-provision File mode RWO volume | GA | >= v1.0.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.14.0 | |
Dynamically provision, de-provision File mode RWOP volume | Alpha | >= v3.5.0 | >= v1.5.0 | Pacific (>=v16.2.0) | >= v1.22.0 | |
Provision File Mode ROX volume from snapshot | Alpha | >= v3.0.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.17.0 | |
Provision File Mode ROX volume from another volume | Alpha | >= v3.0.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.16.0 | |
Provision Block Mode ROX volume from snapshot | Alpha | >= v3.0.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.17.0 | |
Provision Block Mode ROX volume from another volume | Alpha | >= v3.0.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.16.0 | |
Creating and deleting snapshot | GA | >= v1.0.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.17.0 | |
Provision volume from snapshot | GA | >= v1.0.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.17.0 | |
Provision volume from another volume | GA | >= v1.0.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.16.0 | |
Expand volume | Beta | >= v2.0.0 | >= v1.1.0 | Pacific (>=v16.2.0) | >= v1.15.0 | |
Volume/PV Metrics of File Mode Volume | GA | >= v1.2.0 | >= v1.1.0 | Pacific (>=v16.2.0) | >= v1.15.0 | |
Volume/PV Metrics of Block Mode Volume | GA | >= v1.2.0 | >= v1.1.0 | Pacific (>=v16.2.0) | >= v1.21.0 | |
Topology Aware Provisioning Support | Alpha | >= v2.1.0 | >= v1.1.0 | Pacific (>=v16.2.0) | >= v1.14.0 | |
CephFS | Dynamically provision, de-provision File mode RWO volume | GA | >= v1.1.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.14.0 |
Dynamically provision, de-provision File mode RWX volume | GA | >= v1.1.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.14.0 | |
Dynamically provision, de-provision File mode ROX volume | Alpha | >= v3.0.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.14.0 | |
Dynamically provision, de-provision File mode RWOP volume | Alpha | >= v3.5.0 | >= v1.5.0 | Pacific (>=v16.2.0) | >= v1.22.0 | |
Creating and deleting snapshot | GA | >= v3.1.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.17.0 | |
Creating and deleting volume group snapshot | Alpha | >= v3.11.0 | >= v1.9.0 | Squid (>=v19.0.0) | >= v1.31.0 | |
Provision volume from snapshot | GA | >= v3.1.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.17.0 | |
Provision volume from another volume | GA | >= v3.1.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.16.0 | |
Expand volume | Beta | >= v2.0.0 | >= v1.1.0 | Pacific (>=v16.2.0) | >= v1.15.0 | |
Volume/PV Metrics of File Mode Volume | GA | >= v1.2.0 | >= v1.1.0 | Pacific (>=v16.2.0) | >= v1.15.0 | |
NFS | Dynamically provision, de-provision File mode RWO volume | Alpha | >= v3.6.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.14.0 |
Dynamically provision, de-provision File mode RWX volume | Alpha | >= v3.6.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.14.0 | |
Dynamically provision, de-provision File mode ROX volume | Alpha | >= v3.6.0 | >= v1.0.0 | Pacific (>=v16.2.0) | >= v1.14.0 | |
Dynamically provision, de-provision File mode RWOP volume | Alpha | >= v3.6.0 | >= v1.5.0 | Pacific (>=v16.2.0) | >= v1.22.0 | |
Expand volume | Alpha | >= v3.7.0 | >= v1.1.0 | Pacific (>=v16.2.0) | >= v1.15.0 | |
Creating and deleting snapshot | Alpha | >= v3.7.0 | >= v1.1.0 | Pacific (>=v16.2.0) | >= v1.17.0 | |
Provision volume from snapshot | Alpha | >= v3.7.0 | >= v1.1.0 | Pacific (>=v16.2.0) | >= v1.17.0 | |
Provision volume from another volume | Alpha | >= v3.7.0 | >= v1.1.0 | Pacific (>=v16.2.0) | >= v1.16.0 |
NOTE
: The Alpha
status reflects possible non-backward
compatible changes in the future, and is thus not recommended
for production use.
Please refer to the matrix in the Kubernetes documentation.
Ceph CSI Release/Branch | Container image name | Image Tag |
---|---|---|
devel (Branch) | quay.io/cephcsi/cephcsi | canary |
v3.12.0 (Release) | quay.io/cephcsi/cephcsi | v3.12.0 |
v3.11.0 (Release) | quay.io/cephcsi/cephcsi | v3.11.0 |
Deprecated Ceph CSI Release/Branch | Container image name | Image Tag |
---|---|---|
v3.10.2 (Release) | quay.io/cephcsi/cephcsi | v3.10.2 |
v3.10.1 (Release) | quay.io/cephcsi/cephcsi | v3.10.1 |
v3.10.0 (Release) | quay.io/cephcsi/cephcsi | v3.10.0 |
v3.9.0 (Release) | quay.io/cephcsi/cephcsi | v3.9.0 |
v3.8.1 (Release) | quay.io/cephcsi/cephcsi | v3.8.1 |
v3.8.0 (Release) | quay.io/cephcsi/cephcsi | v3.8.0 |
v3.7.2 (Release) | quay.io/cephcsi/cephcsi | v3.7.2 |
v3.7.1 (Release) | quay.io/cephcsi/cephcsi | v3.7.1 |
v3.7.0 (Release) | quay.io/cephcsi/cephcsi | v3.7.0 |
v3.6.1 (Release) | quay.io/cephcsi/cephcsi | v3.6.1 |
v3.6.0 (Release) | quay.io/cephcsi/cephcsi | v3.6.0 |
v3.5.1 (Release) | quay.io/cephcsi/cephcsi | v3.5.1 |
v3.5.0 (Release) | quay.io/cephcsi/cephcsi | v3.5.0 |
v3.4.0 (Release) | quay.io/cephcsi/cephcsi | v3.4.0 |
v3.3.1 (Release) | quay.io/cephcsi/cephcsi | v3.3.1 |
v3.3.0 (Release) | quay.io/cephcsi/cephcsi | v3.3.0 |
v3.2.2 (Release) | quay.io/cephcsi/cephcsi | v3.2.2 |
v3.2.1 (Release) | quay.io/cephcsi/cephcsi | v3.2.1 |
v3.2.0 (Release) | quay.io/cephcsi/cephcsi | v3.2.0 |
v3.1.2 (Release) | quay.io/cephcsi/cephcsi | v3.1.2 |
v3.1.1 (Release) | quay.io/cephcsi/cephcsi | v3.1.1 |
v3.1.0 (Release) | quay.io/cephcsi/cephcsi | v3.1.0 |
v3.0.0 (Release) | quay.io/cephcsi/cephcsi | v3.0.0 |
v2.1.2 (Release) | quay.io/cephcsi/cephcsi | v2.1.2 |
v2.1.1 (Release) | quay.io/cephcsi/cephcsi | v2.1.1 |
v2.1.0 (Release) | quay.io/cephcsi/cephcsi | v2.1.0 |
v2.0.1 (Release) | quay.io/cephcsi/cephcsi | v2.0.1 |
v2.0.0 (Release) | quay.io/cephcsi/cephcsi | v2.0.0 |
v1.2.2 (Release) | quay.io/cephcsi/cephcsi | v1.2.2 |
v1.2.1 (Release) | quay.io/cephcsi/cephcsi | v1.2.1 |
v1.2.0 (Release) | quay.io/cephcsi/cephcsi | v1.2.0 |
v1.1.0 (Release) | quay.io/cephcsi/cephcsi | v1.1.0 |
v1.0.0 (Branch) | quay.io/cephcsi/cephfsplugin | v1.0.0 |
v1.0.0 (Branch) | quay.io/cephcsi/rbdplugin | v1.0.0 |
Please follow development-guide and coding style guidelines if you are interested to contribute to this repo.
Please submit an issue at: Issues
We conduct weekly bug triage calls at our slack channel on Tuesdays. More details are available here
A regular dev standup takes place every Monday at
12:00 PM UTC Convert to your local
timezone by executing command date -d "12:00 UTC"
on terminal
Any changes to the meeting schedule will be added to the agenda doc.
Anyone who wants to discuss the direction of the project, design and implementation reviews, or general questions with the broader community is welcome and encouraged to join.
Please use the following to reach members of the community: