Files
Oded Viner ec502c3f80 nvmeof: use .nvmeof pool for gateway and remove pool field from CRD
Changes:
- Use a dedicated .nvmeof pool (via CephBlockPool CR named
  builtin-nvmeof) for the NVMe-oF gateway internal state.
- Use a separate nvmeof pool for the StorageClass data.
- Remove the pool field from the CephNVMeOFGateway CRD.
  The gateway now always uses the .nvmeof pool, hardcoded
  in the operator.
- Add .nvmeof to the allowed CephBlockPool name overrides.
- Create a production example nvmeof.yaml (instances: 2,
  replicas: 3) and a CI-only nvmeof-test.yaml (instances: 1,
  replicas: 1).
- Update documentation and CI test script accordingly.

Signed-off-by: Oded Viner <oviner@redhat.com>
2026-07-21 20:19:44 +03:00

27 lines
668 B
YAML

# This example is for Ceph v20 and above only
apiVersion: ceph.rook.io/v1
kind: CephBlockPool
metadata:
name: builtin-nvmeof
namespace: rook-ceph # namespace:cluster
spec:
name: .nvmeof
failureDomain: host
replicated:
size: 3
---
apiVersion: ceph.rook.io/v1
kind: CephNVMeOFGateway
metadata:
name: nvmeof
namespace: rook-ceph # namespace:cluster
spec:
# image is optional. If not specified, the image is fetched from the Ceph config store
# (ceph config get mgr mgr/cephadm/container_image_nvmeof).
# Set the image property to override the default:
# image: quay.io/ceph/nvmeof:<version>
group: group-a
instances: 2
hostNetwork: false