Rook (Ceph) - In Cluster

Deploy the Rook operator

kubectl apply -k /etc/genestack/kustomize/rook-operator/

Manually specifying the rook-operator image

Under certain circumstances it may be required to do this, below is an example of how one can pin the operator version if so desired.

kubectl -n rook-ceph set image deploy/rook-ceph-operator rook-ceph-operator=rook/ceph:v1.13.7

Label the Storage Nodes

key	type	value	notes
role	str	`storage-node`	When set to "storage-node" the node will be used for Ceph OSDs

Use the following command to label a node to be part of the Ceph storage cluster:

kubectl label node ${NODE_NAME} role=storage-node

Replace ${NODE_NAME} with the name of your node. If you have multiple storage nodes, run this command against each one.

Deploy the Rook cluster

Note

Rook will deploy against nodes labeled role=storage-node. Make sure to have a look at the /etc/genestack/kustomize/rook-cluster/rook-cluster.yaml file to ensure it's setup to your liking, pay special attention to your deviceFilter settings, especially if different devices have different device layouts.

kubectl apply -k /etc/genestack/kustomize/rook-cluster/overlay

Validate the cluster is operational

kubectl --namespace rook-ceph get cephclusters.ceph.rook.io

Note

You can track the deployment with the following command kubectl --namespace rook-ceph get pods -w.

Create Storage Classes

Once the rook cluster is online with a HEALTH status of HEALTH_OK, deploy the filesystem, storage-class, and pool defaults.

kubectl apply -k /etc/genestack/kustomize/rook-defaults

Note

If installing prometheus after rook-ceph is installed, you may patch a running rook-ceph cluster with the following command.

kubectl -n rook-ceph patch CephCluster rook-ceph  --type=merge -p "{\"spec\": {\"monitoring\": {\"enabled\": true}}}"

Ensure you have 'servicemonitors' defined in the rook-ceph namespace.