In the latest enhancement to Rook’s Ceph operator, users can now explicitly specify the clusterID when creating CephBlockPoolRadosNamespace and CephFilesystemSubVolumeGroup custom resources. This update gives users more control and flexibility over how storage clusters are identified and referenced by the CSI driver.

This blog will help you to Understand how to consume storage from external ceph cluster in Rook and how to create and consume Below listed resources in the ceph cluster.

This doc assumes that you already set up the rbd mirroring between two clusters.

The issue in Provisioning the CephFS/RBD PVC or Mounting the CephFS/RBD PVC to application pods can happen for Many reasons like Network connectivity between csi pods and ceph, cluster health issue,Slow operations, kubernetes issue, etc. Even the issue can be at the Ceph-CSI layer itself. Hope the below-documented steps might help you to understand and Debug the cephcsi issues.

This doc assumes that you already have a minikube installed, minikube is configured to use kvm2 to create a virtual machine. You can refer kvm2 to install the required prerequisites.

This blog will help you out understand the various configuration we need to do to manage the external ceph cluster with Rook.

This blog will help you to understand how to track the internal rados omap data stored by cephcsi for cephfs and rbd pvc.

This blog will help you out to install and setup rook in a minikube vm, before you continue make sure you have installed minikube on your local system