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

推荐订阅源

月光博客
月光博客
Stack Overflow Blog
Stack Overflow Blog
L
LangChain Blog
Jina AI
Jina AI
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
雷峰网
雷峰网
T
Tailwind CSS Blog
MongoDB | Blog
MongoDB | Blog
博客园 - 【当耐特】
博客园 - 聂微东
V
Visual Studio Blog
博客园_首页
Engineering at Meta
Engineering at Meta
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
The Cloudflare Blog
人人都是产品经理
人人都是产品经理
Apple Machine Learning Research
Apple Machine Learning Research
阮一峰的网络日志
阮一峰的网络日志
Microsoft Security Blog
Microsoft Security Blog
GbyAI
GbyAI
F
Fortinet All Blogs
C
Check Point Blog
罗磊的独立博客
H
Hackread – Cybersecurity News, Data Breaches, AI and More

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 Rook-Ceph with Zero Downtime
Nawaz Dhandala · 2026-03-31 · via OneUptime Blog

Zero-downtime upgrades in Rook require upgrading the operator first, then allowing it to rolling-update Ceph daemons in the correct order. PVCs remain accessible throughout if the cluster is healthy before starting.

Upgrade Order

flowchart TD
    A[Pre-upgrade validation] --> B[Upgrade Rook operator]
    B --> C[Operator upgrades MON daemons]
    C --> D[Operator upgrades MGR daemons]
    D --> E[Operator upgrades OSD daemons]
    E --> F[Operator upgrades MDS daemons]
    F --> G[Operator upgrades RGW daemons]
    G --> H[Post-upgrade validation]
    H --> I[Cluster HEALTH_OK]

Pre-Upgrade Checklist

# 1. Confirm cluster is HEALTH_OK
kubectl exec -n rook-ceph deploy/rook-ceph-tools -- ceph status
kubectl exec -n rook-ceph deploy/rook-ceph-tools -- ceph health detail

# 2. Check all OSDs are up and in
kubectl exec -n rook-ceph deploy/rook-ceph-tools -- ceph osd stat
# "X osds: X up, X in" (no down or out)

# 3. Confirm no PGs degraded
kubectl exec -n rook-ceph deploy/rook-ceph-tools -- ceph pg stat
# active+clean for all PGs

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

# 5. Check current Ceph version
kubectl exec -n rook-ceph deploy/rook-ceph-tools -- ceph version

Disable PG Auto-Scrub During Upgrade (Optional)

kubectl exec -n rook-ceph deploy/rook-ceph-tools -- \
  ceph osd set noscrub

kubectl exec -n rook-ceph deploy/rook-ceph-tools -- \
  ceph osd set nodeep-scrub

Upgrade the Rook Operator

Using Helm

# Check current chart version
helm list -n rook-ceph

# Update repo
helm repo update rook-release

# Check available versions
helm search repo rook-release/rook-ceph --versions | head -10

# Upgrade operator (example: v1.13.x to v1.14.x)
helm upgrade rook-ceph rook-release/rook-ceph \
  --namespace rook-ceph \
  --version v1.14.0 \
  --reuse-values

# Monitor operator pod
kubectl rollout status deployment rook-ceph-operator -n rook-ceph

Using kubectl (manifest)

# Download the new operator manifest
curl -O https://raw.githubusercontent.com/rook/rook/v1.14.0/deploy/examples/operator.yaml

# Review changes before applying
kubectl diff -f operator.yaml

# Apply the new operator
kubectl apply -f operator.yaml

# Watch operator rollout
kubectl rollout status deployment rook-ceph-operator -n rook-ceph

Upgrade the Ceph Version

Update the Ceph image in the CephCluster spec:

apiVersion: ceph.rook.io/v1
kind: CephCluster
metadata:
  name: rook-ceph
  namespace: rook-ceph
spec:
  cephVersion:
    image: quay.io/ceph/ceph:v18.2.4   # New Ceph Reef version
    allowUnsupported: false
kubectl apply -f cephcluster.yaml

# Watch daemon rolling update
kubectl get pods -n rook-ceph -w | grep -v Running

Monitor the Rolling Upgrade

# Watch MONs update first
kubectl get pods -n rook-ceph -l app=rook-ceph-mon -w

# Then MGR
kubectl get pods -n rook-ceph -l app=rook-ceph-mgr -w

# Then OSDs (one at a time)
kubectl get pods -n rook-ceph -l app=rook-ceph-osd -w

# Cluster should remain HEALTH_OK or HEALTH_WARN during OSD rolling updates
watch kubectl exec -n rook-ceph deploy/rook-ceph-tools -- ceph status

Verify Each Daemon After Upgrade

# Check MON versions
kubectl exec -n rook-ceph deploy/rook-ceph-tools -- ceph versions

# Should show:
# {
#   "mon": {"ceph version 18.2.4 ...": 3},
#   "mgr": {"ceph version 18.2.4 ...": 2},
#   "osd": {"ceph version 18.2.4 ...": 9},
#   "mds": {"ceph version 18.2.4 ...": 2}
# }

# Upgrade is complete when all daemons show the new version

Post-Upgrade Validation

# Re-enable scrub
kubectl exec -n rook-ceph deploy/rook-ceph-tools -- \
  ceph osd unset noscrub
kubectl exec -n rook-ceph deploy/rook-ceph-tools -- \
  ceph osd unset nodeep-scrub

# Final health check
kubectl exec -n rook-ceph deploy/rook-ceph-tools -- ceph status
kubectl exec -n rook-ceph deploy/rook-ceph-tools -- ceph health detail

# Verify PVCs still accessible
kubectl get pvc --all-namespaces | grep Bound

Summary

Zero-downtime Rook-Ceph upgrades require a healthy cluster as the starting point, followed by upgrading the Rook operator, then updating the Ceph version image in the CephCluster CR. The operator handles the rolling update of all daemons in the correct order (MON, MGR, OSD, MDS, RGW). Monitor ceph status throughout and disable scrub during the OSD rolling update to reduce overhead. Always validate cluster health before and after each stage.