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

推荐订阅源

让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
V
V2EX
WordPress大学
WordPress大学
U
Unit 42
I
InfoQ
A
About on SuperTechFans
宝玉的分享
宝玉的分享
J
Java Code Geeks
博客园 - 司徒正美
爱范儿
爱范儿
Engineering at Meta
Engineering at Meta
G
Google Developers Blog
人人都是产品经理
人人都是产品经理
小众软件
小众软件
Microsoft Security Blog
Microsoft Security Blog
L
LangChain Blog
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Hugging Face - Blog
Hugging Face - Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
aimingoo的专栏
aimingoo的专栏
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
Last Week in AI
Last Week in AI
腾讯CDC
Recent Announcements
Recent Announcements

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 Create a Ceph Upgrade Runbook
Nawaz Dhandala · 2026-03-31 · via OneUptime Blog

Pre-Upgrade Checklist

Before starting any upgrade, verify the cluster is healthy:

kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- ceph status
kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- ceph health detail
kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- ceph osd stat

All conditions must be true:

  • Cluster is HEALTH_OK
  • No OSDs are down or out
  • All PGs are active+clean
  • No ongoing recovery operations

Step 1: Update CRDs

CRDs must be updated before the operator upgrade. The new operator may depend on CRD fields that do not exist yet, so always apply CRDs first:

kubectl apply -f https://raw.githubusercontent.com/rook/rook/v1.14.0/deploy/examples/crds.yaml

Verify the CRDs were updated:

kubectl get crd | grep ceph

Step 2: Upgrade the Rook Operator

With CRDs in place, upgrade the Rook operator. Use the Helm upgrade:

helm repo update
helm upgrade rook-ceph rook-release/rook-ceph \
  --namespace rook-ceph \
  --version v1.14.0 \
  -f values.yaml

Or apply the updated operator manifests directly:

kubectl -n rook-ceph apply -f https://raw.githubusercontent.com/rook/rook/v1.14.0/deploy/examples/operator.yaml

Monitor the operator rollout:

kubectl -n rook-ceph rollout status deploy/rook-ceph-operator

Step 3: Update the Ceph Image Version

Edit the CephCluster resource to bump the Ceph image:

spec:
  cephVersion:
    image: quay.io/ceph/ceph:v18.2.4
    allowUnsupported: false

Apply the change:

kubectl -n rook-ceph apply -f ceph-cluster.yaml

Step 4: Monitor the Upgrade Progress

The Rook operator performs a rolling upgrade of all Ceph daemons:

watch kubectl -n rook-ceph get pods

Check the upgrade status via the CephCluster status:

kubectl -n rook-ceph get cephcluster rook-ceph -o jsonpath='{.status.ceph}' | python3 -m json.tool

Step 5: Post-Upgrade Validation

kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- ceph version
kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- ceph status
kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- ceph osd versions
kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- ceph mon versions
kubectl -n rook-ceph exec -it deploy/rook-ceph-tools -- ceph mgr versions

Ensure all daemons report the new version.

Rollback Procedure

If the upgrade causes issues, revert the Ceph image in the CephCluster spec and re-apply. Rook will roll back the daemon versions. Note that Ceph downgrades are not always safe - if internal data formats were upgraded during the new version's startup, reverting the image may cause issues. Test rollback procedures in a non-production environment first:

kubectl -n rook-ceph patch cephcluster rook-ceph --type merge \
  -p '{"spec":{"cephVersion":{"image":"quay.io/ceph/ceph:v18.2.2"}}}'

Summary

A Ceph upgrade runbook ensures every step is documented and repeatable. The sequence is: validate health, update CRDs, upgrade the operator, bump the Ceph image, and confirm all daemons are running the new version. Always verify cluster health before and after each phase.