External Cluster Options¶
NFS storage¶
Rook suggests a different mechanism for making use of an NFS service running on the external Ceph standalone cluster, if desired.
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.
-
Copy create-external-cluster-resources.py into the directory
/etc/ceph/
of the toolbox. -
Exec to the toolbox pod and execute create-external-cluster-resources.py with needed options to create required users and keys.
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.
Admin privileges¶
If in case the cluster needs the admin keyring to configure, update the admin key rook-ceph-mon
secret with client.admin keyring
Note
Sharing the admin key with the external cluster is not generally recommended
-
Get the
client.admin
keyring from the ceph cluster -
Update two values in the
rook-ceph-mon
secret:ceph-username
: Set toclient.admin
ceph-secret
: Set the client.admin keyring
After restarting the rook operator (and the toolbox if in use), rook will configure ceph with admin privileges.
Connect to an External Object Store¶
Create the external object store CR to configure connection to external gateways.
Consume the S3 Storage, in two different ways:
-
Create an Object store user for credentials to access the S3 endpoint.
-
Create a bucket storage class where a client can request creating buckets and then create the Object Bucket Claim, which will create an individual bucket for reading and writing objects.
Hint
For more details see the Object Store topic