2064e674a4
Based on the review comments addressed the following, - Moved away from having to update the pod with volumes when a new Ceph cluster is added for provisioning via the CSI driver - The above now used k8s APIs to fetch secrets - TBD: Need to add a watch mechanisim such that these secrets can be cached and updated when changed - Folded the Cephc configuration and ID/key config map and secrets into a single secret - Provided the ability to read the same config via mapped or created files within the pod Tests: - Ran PV creation/deletion/attach/use using new scheme StorageClass - Ran PV creation/deletion/attach/use using older scheme to ensure nothing is broken - Did not execute snapshot related tests Signed-off-by: ShyamsundarR <srangana@redhat.com> |
||
---|---|---|
cmd | ||
deploy | ||
docs | ||
examples | ||
pkg | ||
scripts | ||
vendor | ||
.gitignore | ||
.mergify.yml | ||
.travis.yml | ||
deploy.sh | ||
Gopkg.lock | ||
Gopkg.toml | ||
LICENSE | ||
Makefile | ||
README.md |
Ceph CSI 1.0.0
Container Storage Interface (CSI) driver, provisioner, and attacher for Ceph RBD and CephFS.
Overview
Ceph CSI plugins implement an interface between CSI enabled Container Orchestrator (CO) and CEPH cluster. It allows dynamically provisioning CEPH volumes and attaching them to workloads. Current implementation of Ceph CSI plugins was tested in Kubernetes environment (requires Kubernetes 1.13+), but the code does not rely on any Kubernetes specific calls (WIP to make it k8s agnostic) and should be able to run with any CSI enabled CO.
For details about configuration and deployment of RBD and
CephFS CSI plugins, see documentation in docs/
.
For example usage of RBD and CephFS CSI plugins, see examples in examples/
.
Troubleshooting
Please submit an issue at: Issues
Slack Channels
Join us at Rook ceph-csi Channel