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

推荐订阅源

I
InfoQ
G
Google Developers Blog
Engineering at Meta
Engineering at Meta
月光博客
月光博客
博客园 - 聂微东
博客园 - Franky
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
有赞技术团队
有赞技术团队
A
About on SuperTechFans
Microsoft Azure Blog
Microsoft Azure Blog
Blog — PlanetScale
Blog — PlanetScale
U
Unit 42
T
Tailwind CSS Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
云风的 BLOG
云风的 BLOG
S
SegmentFault 最新的问题
F
Fortinet All Blogs
H
Help Net Security
J
Java Code Geeks
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - 叶小钗
L
LangChain Blog
Martin Fowler
Martin Fowler
N
Netflix TechBlog - Medium

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 Complete Rook-Ceph Cleanup How to Verify Backup Integrity from Ceph Snapshots
How to Upgrade from Ceph Quincy to Reef
Nawaz Dhandala · 2026-03-31 · via OneUptime Blog

Upgrading from Ceph Quincy (v17) to Reef (v18) is a supported upgrade path. With Rook managing the cluster, the upgrade process is largely automated but requires careful preparation and monitoring to ensure a smooth transition.

Pre-Upgrade Checklist

Before starting the upgrade:

# 1. Verify current Ceph version
kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- ceph version
# Should show: ceph version 17.x.x ... quincy

# 2. Verify cluster health
kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- ceph health detail
# Must be HEALTH_OK before proceeding

# 3. Check all OSDs are up
kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- ceph osd stat
# All OSDs should be up and in

# 4. Verify no ongoing recovery
kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- ceph pg stat
# Should show: 0 degraded, 0 misplaced, 0 recovering

# 5. Check Rook version supports Reef
kubectl -n rook-ceph get deploy rook-ceph-operator \
  -o jsonpath='{.spec.template.spec.containers[0].image}'
# Rook v1.12+ required for Ceph v18 (Reef)

Upgrade Rook Operator First

Always upgrade Rook before upgrading Ceph:

# Check current Rook version
kubectl -n rook-ceph get deploy rook-ceph-operator \
  -o jsonpath='{.spec.template.spec.containers[0].image}'

# Upgrade Rook operator to v1.13 (supports Reef)
helm repo update
helm upgrade rook-ceph rook-release/rook-ceph \
  --namespace rook-ceph \
  --version v1.13.0

# Wait for operator to be ready
kubectl -n rook-ceph rollout status deploy/rook-ceph-operator --timeout=120s

Upgrade the Ceph Cluster

Update the CephCluster spec to point to the Reef image:

apiVersion: ceph.rook.io/v1
kind: CephCluster
metadata:
  name: rook-ceph
  namespace: rook-ceph
spec:
  cephVersion:
    image: quay.io/ceph/ceph:v18.2.0  # Change from v17.x.x
    allowUnsupported: false
# Apply the change
kubectl apply -f ceph-cluster.yaml

# OR use kubectl patch
kubectl -n rook-ceph patch CephCluster rook-ceph \
  --type merge \
  -p '{"spec":{"cephVersion":{"image":"quay.io/ceph/ceph:v18.2.0"}}}'

Monitoring the Upgrade

#!/bin/bash
# monitor-upgrade.sh

NAMESPACE="${CEPH_NAMESPACE:-rook-ceph}"

echo "Monitoring Ceph upgrade..."
while true; do
  echo "=== $(date) ==="

  # Check version distribution
  kubectl -n "$NAMESPACE" exec deploy/rook-ceph-tools -- \
    ceph versions 2>/dev/null

  # Check cluster health
  HEALTH=$(kubectl -n "$NAMESPACE" exec deploy/rook-ceph-tools -- \
    ceph health 2>/dev/null)
  echo "Health: $HEALTH"

  # Check if all daemons are upgraded
  ALL_V18=$(kubectl -n "$NAMESPACE" exec deploy/rook-ceph-tools -- \
    ceph versions --format json 2>/dev/null | \
    python3 -c "
import sys, json
d = json.load(sys.stdin)
all_counts = sum(d.get('overall',{}).values())
v18_keys = [k for k in d.get('overall',{}) if 'reef' in k or '18.' in k]
v18_count = sum(d['overall'][k] for k in v18_keys)
print(f'{v18_count}/{all_counts} daemons on Reef')
" 2>/dev/null)
  echo "Upgrade progress: $ALL_V18"

  sleep 30
done

Post-Upgrade Validation

# Verify all daemons are on Reef
kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- ceph versions
# All entries should show reef/v18

# Run full health check
kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- ceph health detail

# Verify OSD functionality
kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- bash -c "
# Write and read test objects
rados -p .mgr put upgrade-test /etc/hostname
rados -p .mgr get upgrade-test /tmp/upgrade-verify
diff /etc/hostname /tmp/upgrade-verify && echo 'Data integrity: OK'
rados -p .mgr rm upgrade-test
"

# Verify CSI drivers are updated
kubectl -n rook-ceph get pods -l app=csi-rbdplugin -o wide

Rollback Procedure

If issues arise, rollback by reverting the image:

# Note: rolling back Ceph is generally not safe if OSDs have written data
# Only roll back if upgrade stalls before any OSD is upgraded

# Check if rollback is safe
kubectl -n rook-ceph exec deploy/rook-ceph-tools -- \
  ceph versions --format json | python3 -c "
import sys, json
d = json.load(sys.stdin)
print('Daemon versions:', json.dumps(d, indent=2))
"

# Rollback if safe (only monitors/mgr upgraded, no OSDs)
kubectl -n rook-ceph patch CephCluster rook-ceph \
  --type merge \
  -p '{"spec":{"cephVersion":{"image":"quay.io/ceph/ceph:v17.2.7"}}}'

Summary

Upgrading from Ceph Quincy to Reef with Rook involves upgrading the Rook operator first, then updating the CephCluster spec with the new image tag. Rook handles the rolling upgrade of all daemons in the correct order. Pre-upgrade health verification and continuous monitoring during the upgrade are the keys to a successful transition, and rollback is possible if issues arise before OSDs are upgraded.