No, my understanding was that you can give clients access to RBD's through the nvme-gateway, they see it as an nvme drive. And due to Aviv's help on slack I was able to confirm this understanding, I have a single node ceph cluster (virtual machine), deployed nvme-of and see the RBD image as an nvme drive within the VM now: test:~ # nvme list Node Generic SN Model Namespace Usage Format FW Rev --------------------- --------------------- -------------------- ---------------------------------------- ---------- -------------------------- ---------------- -------- /dev/nvme1n1 /dev/ng1n1 Ceph42382366687857 Ceph bdev Controller 0x1 10.74 GB / 10.74 GB 512 B + 0 B 25.05.1 Zitat von Alexander Schreiber <als@thangorodrim.ch>:
On Mon, Apr 13, 2026 at 09:34:39AM +0000, Ernesto Puerta via ceph-users wrote:
Hey Eugen,
AFAIK the Ceph NVMe-oF Gateway superseded the iSCSI one: it's actively maintained, more performant, scalable, secure and better integrated with the Ceph management & observability framework.
I'm curious: what's the target platform/use case for iSCSI that NVMe/TCP cannot fulfill?
As someone who is running pure spinning rust Ceph clusters, I assume the NVMe-oF gateway requires actual NVMe devices to be used for backing, given that the docs mention sending NMVe commands to targets, correct?
Handing out iSCSI devices sounds useful as backing storage for VMs (and some can even boot off it).
Kind regards, Alex. -- "Opportunity is missed by most people because it is dressed in overalls and looks like work." -- Thomas A. Edison