feedc0de/my-rook-config
1
0
Fork 0
forked from rook/rook
Code Pull Requests Activity

docs: import external K8s cluster on existing cluster

Browse Source 
If there is a external k8s cluster which need to use rook-ceph as
a storageclass backend then user can do the following steps import
it to the running rook-ceph cluster

Closes:https://github.com/rook/rook/issues/11404
Signed-off-by: parth-gr <paarora@redhat.com>
This commit is contained in:
parth-gr
2022-12-15 20:11:18 +05:30
parent 4208587b24
commit 8d6be0bcf3
1 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Documentation/CRDs/Cluster/external-cluster.md
+15
View File
@@ -163,3 +163,18 @@ spec:
cephVersion:
image: quay.io/ceph/ceph:v17.2.5 # Should match external cluster version
```
## Exporting Rook to another cluster
If you have multiple K8s clusters running, and want to use the local `rook-ceph` cluster as the central storage,
you can export the settings from this cluster with the following steps.
1) Copy create-external-cluster-resources.py into the directory `/etc/ceph/` of the toolbox.
```console
toolbox=$(kubectl get pod -l app=rook-ceph-tools -n rook-ceph -o jsonpath='{.items[*].metadata.name}')
kubectl -n rook-ceph cp deploy/examples/create-external-cluster-resources.py $toolbox:/etc/ceph
```
2) Exec to the toolbox pod and execute create-external-cluster-resources.py with needed options to create required [users and keys](#supported-features).
!!! important
For other clusters to connect to storage in this cluster, Rook must be configured with a networking configuration that is accessible from other clusters. Most commonly this is done by enabling host networking in the CephCluster CR so the Ceph daemons will be addressable by their host IPs.