High-level workflow of Ceph OSD or node removal¶
Warning
This procedure is valid for MOSK clusters that use the MiraCeph custom
resource (CR), which is available since MOSK 25.2 to replace the unsupported
KaaSCephCluster resource. And MiraCeph will be automatically migrated
to CephDeployment in MOSK 26.1. For details, see Deprecation Notes:
KaaSCephCluster API on management clusters.
For the equivalent procedure with the unsupported KaaSCephCluster CR, refer
to the following section:
The Ceph LCM automated operations such as Ceph OSD or Ceph node removal are
performed by creating a corresponding CephOsdRemoveRequest CR. It allows
for automated removal of healthy or non-healthy Ceph OSDs from a Ceph cluster
and covers the following scenarios:
Reducing hardware - all Ceph OSDs are up/in but you want to decrease the number of Ceph OSDs by reducing the number of disks or hosts.
Hardware issues. For example, if a host unexpectedly goes down and will not be restored, or if a disk on a host goes down and requires replacement.
This section describes the CephOsdRemoveRequest CR creation workflow,
specification, and request status.
For step-by-step procedures, refer to Automated Ceph LCM.