...
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
# The file is located in the folder "rook/clusterdeploy/examples/kubernetes/ceph" $ kubectl create -f toolbox.yaml # Once the rook-ceph-tools pod is running, you can connect to it with $ kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- bash |
...
When you are done with the toolbox, you can remove the deployment kubectl -n deployment with
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
$ kubectl -n rook-ceph delete deploy/rook-ceph-tools |
...
Ceph Dashboard
The dashboard is a very helpful tool to give you an overview of the status of your Ceph cluster, including overall health, status of the mon quorum, status of the mgr, osd, and other Ceph daemons, view pools and PG status, show logs for the daemons, and more.
...
Each Rook Ceph cluster has some built in metrics collectors/exporters for monitoring with Prometheus. If you do not have Prometheus running, follow the steps presented here, to enable monitoring of Rook.
...
Save the file and create the component. The release: prometheus
label that we have introduced serves so that the Prometheus operator can "see" the serviceMonitorservice monitor. How do I find out which label is used by Prometheus? Try running a describe and look for the ServiceMonitorSelector Service Monitor Selector
parameter. The serviceMonitorservice monitor, in turn, points to the components it wants to analyze thanks to the parameters namespaceSelector
and selector
.
...