惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

The GitHub Blog
The GitHub Blog
雷峰网
雷峰网
小众软件
小众软件
博客园 - 【当耐特】
J
Java Code Geeks
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
Hugging Face - Blog
Hugging Face - Blog
腾讯CDC
Engineering at Meta
Engineering at Meta
aimingoo的专栏
aimingoo的专栏
A
About on SuperTechFans
H
Help Net Security
博客园_首页
P
Proofpoint News Feed
GbyAI
GbyAI
大猫的无限游戏
大猫的无限游戏
N
Netflix TechBlog - Medium
爱范儿
爱范儿
MyScale Blog
MyScale Blog
Blog — PlanetScale
Blog — PlanetScale
The Cloudflare Blog
MongoDB | Blog
MongoDB | Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
Google DeepMind News
Google DeepMind News

OneUptime Blog

How to Monitor Azure App Services (PaaS) with OpenTelemetry Grafana Stack vs OneUptime: DIY Observability or Unified Platform? Your AI Workloads Are About to Blow Up Your Observability Bill The Great Observability Consolidation Is Here How to Write Custom Object Classes for Ceph How to Write Custom Ceph Manager Modules How to Write a ceph.conf Configuration File How to Use Rook-Ceph with OpenShift How to Use Rook-Ceph with Longhorn for Comparison How to Configure Volume Snapshot Class for RBD in Rook How to Configure VolumeReplicationClass Scheduling Intervals in Rook How to Set Up Volume Replication with Rook-Ceph How to Create Volume Group Snapshots with Rook CSI How to Visualize Ceph Network Performance in Grafana How to Enable Virtual Host-Style Bucket Access in Rook How to View Runtime Configuration via Admin Socket How to View Quota Settings and Update Stats in Ceph RGW How to View PG Scaling Recommendations with autoscale-status How to View PG Distribution via Admin Socket How to View Performance Metrics in the Ceph Dashboard How to View OSD Performance Counters in Ceph How to View Connection Status via Admin Socket How to View Ceph Cluster Summary Dashboard via CLI How to Version Control Rook-Ceph Configuration How to Version Control Ceph Infrastructure with Terraform How to Verify Kubernetes Node Requirements for Rook-Ceph Deployment How to Verify Health Before and After Rook Upgrades How to Verify Data Integrity with Deep Scrubbing How to Verify Backup Integrity from Ceph Snapshots How to Use Rook-Ceph with Velero for Kubernetes Backup
How to Verify Complete Rook-Ceph Cleanup
Nawaz Dhandala · 2026-03-31 · via OneUptime Blog

After removing a Rook-Ceph cluster, it is essential to verify that all components have been cleaned up before declaring the process complete or attempting a reinstallation. Incomplete cleanup is the most common cause of failed Rook reinstallations. This guide provides a comprehensive verification checklist.

Layer 1: Kubernetes Resources

Start by verifying all Kubernetes-level resources are removed.

Namespace

kubectl get namespace rook-ceph

Expected: Error from server (NotFound) or empty output.

Custom Resources

kubectl get crd | grep -E "rook|ceph"

Expected: No output (all Rook CRDs removed).

Cluster-Scoped Resources

kubectl get clusterrole | grep rook
kubectl get clusterrolebinding | grep rook
kubectl get storageclass | grep rook

Expected: No output for each command.

PersistentVolumes

kubectl get pv | grep -E "rook|ceph"

Expected: No output, or only Released PVs if you are intentionally keeping data.

Secrets and ConfigMaps (cluster-scoped)

kubectl get secret -A | grep rook
kubectl get configmap -A | grep rook

Expected: No output.

Layer 2: Node-Level State

SSH to each storage node and verify the following.

Host Data Directory

for node in node-1 node-2 node-3 node-4 node-5 node-6; do
  echo "=== $node: dataDirHostPath ==="
  ssh $node "ls -la /var/lib/rook/ 2>/dev/null || echo 'Directory absent'"
done

Expected: Empty directory or directory absent on each node.

Running Processes

for node in node-1 node-2 node-3 node-4 node-5 node-6; do
  echo "=== $node: Ceph processes ==="
  PROCS=$(ssh $node "ps aux | grep -E 'ceph-mon|ceph-osd|ceph-mgr|ceph-mds' | grep -v grep")
  if [ -n "$PROCS" ]; then
    echo "WARNING: Ceph processes still running on $node:"
    echo "$PROCS"
  else
    echo "OK: No Ceph processes"
  fi
done

Expected: "OK: No Ceph processes" on each node.

Disk State

for node in node-1 node-2 node-3; do
  echo "=== $node: Disk labels ==="
  ssh $node "sudo wipefs /dev/sdb /dev/sdc /dev/sdd 2>/dev/null"
done

Expected: No output (no filesystem or Ceph labels on disks).

LVM State

for node in node-1 node-2 node-3; do
  echo "=== $node: LVM ==="
  PVS=$(ssh $node "sudo pvs 2>/dev/null | grep ceph || true")
  VGS=$(ssh $node "sudo vgs 2>/dev/null | grep ceph || true")
  if [ -n "$PVS" ] || [ -n "$VGS" ]; then
    echo "WARNING: LVM Ceph volumes remain on $node"
    echo "$PVS"
    echo "$VGS"
  else
    echo "OK: No Ceph LVM volumes"
  fi
done

Expected: "OK: No Ceph LVM volumes" on each node.

Kernel Modules

for node in node-1 node-2 node-3; do
  echo "=== $node: Kernel modules ==="
  MODS=$(ssh $node "lsmod | grep -E 'rbd|ceph' || true")
  if [ -n "$MODS" ]; then
    echo "WARNING: Ceph kernel modules still loaded on $node:"
    echo "$MODS"
  else
    echo "OK: No Ceph kernel modules"
  fi
done

Layer 3: Automated Verification Script

Combine all checks into a single verification script:

#!/bin/bash

set -euo pipefail

NODES="${NODES:-node-1 node-2 node-3}"
PASS=0
FAIL=0

check() {
  local description="$1"
  local command="$2"
  local expected_empty="${3:-true}"

  RESULT=$(eval "$command" 2>/dev/null || true)
  if [ "$expected_empty" = "true" ] && [ -z "$RESULT" ]; then
    echo "PASS: $description"
    PASS=$((PASS + 1))
  elif [ "$expected_empty" = "true" ] && [ -n "$RESULT" ]; then
    echo "FAIL: $description"
    echo "  Found: $RESULT"
    FAIL=$((FAIL + 1))
  fi
}

echo "=== Kubernetes Layer ==="
check "rook-ceph namespace removed" "kubectl get namespace rook-ceph -o name"
check "Rook CRDs removed" "kubectl get crd -o name | grep -E 'rook|ceph'"
check "Rook ClusterRoles removed" "kubectl get clusterrole -o name | grep rook"
check "Rook StorageClasses removed" "kubectl get storageclass -o name | grep rook"
check "Rook PersistentVolumes removed" "kubectl get pv -o name | grep rook"

echo ""
echo "=== Node Layer ==="
for node in $NODES; do
  check "$node: dataDirHostPath empty" "ssh $node 'ls /var/lib/rook/ 2>/dev/null'"
  check "$node: No Ceph processes" "ssh $node 'ps aux | grep -E ceph-mon\|ceph-osd | grep -v grep'"
  check "$node: No Ceph kernel modules" "ssh $node 'lsmod | grep -E rbd\|ceph'"
done

echo ""
echo "=== Summary ==="
echo "PASS: $PASS"
echo "FAIL: $FAIL"

if [ "$FAIL" -eq 0 ]; then
  echo "Cleanup COMPLETE. Ready for fresh installation."
  exit 0
else
  echo "Cleanup INCOMPLETE. Address failures before reinstalling."
  exit 1
fi

Summary

Verifying complete Rook-Ceph cleanup requires checking three layers: Kubernetes resources (namespace, CRDs, ClusterRoles, StorageClasses, PVs), node-level state (dataDirHostPath, Ceph processes, disk labels, LVM volumes, kernel modules), and confirming no orphaned secrets or configmaps remain. Use an automated verification script to check all layers systematically before declaring cleanup complete or attempting reinstallation. Any remaining artifacts will cause the new installation to conflict with the old cluster state.