Draft
Conversation
418d06f to
f92fd75
Compare
6 tasks
The NVMe-oF Ceph-CSI driver is a work in progress, and expected to be ready for testing soon. Because Ceph-CSI will recommend the Ceph-CSI Operator for deploying, it will need to support the new NVMe-oF driver type as well. Signed-off-by: Niels de Vos <[email protected]>
Signed-off-by: Niels de Vos <[email protected]>
Signed-off-by: Niels de Vos <[email protected]>
Only the canary image currently supports snapshots with NVMe-oF. Older releases do not support it, and the csi-snapshotter sidecar gets into an error state. Signed-off-by: Niels de Vos <[email protected]>
f92fd75 to
43d3ee5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe what this PR does
The NVMe-oF Ceph-CSI driver is a work in progress, and expected to be ready for testing soon. Because Ceph-CSI will recommend the Ceph-CSI Operator for deploying, it will need to support the new NVMe-oF driver type as well.
Is there anything that requires special attention
Internally the NVMe-oF driver in Ceph-CSI calls the functions of the RBD CSI Controller. That means almost all permissions and requirements that are valid for RBD, are also required for NVMe-oF.
The initial NVMe-oF driver will only support basic functions. Additional features like snapshots, resizing and CSI-Addons procedures will be added later.
The NVMe-oF gateway can not yet be deployed by Rook. This makes testing a manual effort for now.
Related issues
See-also: #304 ceph/ceph-csi#5370 rook/rook#16950
Future concerns
In order to use Ceph-CSI with NVMe-oF, one needs a Ceph Tentacle cluster (for the ceph-nvme gateway) and these current images:
quay.io/cephcsi/cephcsi:canarygcr.io/k8s-staging-sig-storage/csi-provisioner:canarygcr.io/k8s-staging-sig-storage/csi-resizer:canaryThe Kubernetes CSI images are required for the VolumeAttributeClass support (the ceph-nvme gateway supports QoS, implemented in Ceph-CSI through the new
ControllerModifyVolumeCSI procedure).Checklist:
guidelines in the developer
guide.
Request
notes
updated with breaking and/or notable changes for the next major release.