...
If you did not modify the cluster.yaml above, it is expected that one OSD will be created per node. The file, which is fine in most cases, contains many parameters that can be changed. Here you will find a detailed list.
Cleanup
If you want to tear down the cluster and bring up a new one, be aware of the following resources that will need to be cleaned up:
rook-cephnamespace: The Rook operator and cluster created byoperator.yamlandcluster.yaml(the cluster CRD);/var/lib/rook: Path on each host in the cluster where configuration is cached by the ceph mons and osds.
| Info | ||
|---|---|---|
|
...
If you changed the default namespaces or paths such as |
A namespace cannot be removed until all of its resources are removed. Therefore, to eliminate it, we execute the commands in the following order
| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
$ kubectl -n rook-ceph delete cephcluster rook-ceph
# Verify that the cluster CRD has been deleted before continuing to the next step.
# Remember that the path of the following files is "rook/cluster/examples/kubernetes/ceph".
$ kubectl delete -f operator.yaml
$ kubectl delete -f common.yaml
$ kubectl delete -f crds.yaml |
At this point connect to each machine and delete /var/lib/rook, or the path specified by the dataDirHostPath. If the cleanup instructions are not executed in the order above, or you otherwise have difficulty cleaning up the cluster, here are a few things to try.