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

推荐订阅源

美团技术团队
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Martin Fowler
Martin Fowler
雷峰网
雷峰网
IT之家
IT之家
小众软件
小众软件
M
MIT News - Artificial intelligence
博客园 - 聂微东
J
Java Code Geeks
Blog — PlanetScale
Blog — PlanetScale
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
A
About on SuperTechFans
G
Google Developers Blog
Engineering at Meta
Engineering at Meta
Recent Announcements
Recent Announcements
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
The GitHub Blog
The GitHub Blog
F
Fortinet All Blogs
C
Check Point Blog
云风的 BLOG
云风的 BLOG
腾讯CDC
H
Help Net Security
Y
Y Combinator Blog
I
InfoQ

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 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 Use Rook-Ceph with Velero for Kubernetes Backup
How to Version Control Ceph Infrastructure with Terraform
Nawaz Dhandala · 2026-03-31 · via OneUptime Blog

Version controlling your Ceph infrastructure with Terraform means every change is reviewed, tested, and auditable. This guide covers remote state management, module organization, and CI/CD integration for Ceph clusters.

Repository Structure

ceph-infra/
  environments/
    dev/
      main.tf
      terraform.tfvars
    staging/
      main.tf
      terraform.tfvars
    prod/
      main.tf
      terraform.tfvars
  modules/
    ceph-cluster/
      main.tf
      variables.tf
      outputs.tf
    ceph-pool/
      main.tf
      variables.tf
    ceph-object-store/
      main.tf
      variables.tf
  .github/
    workflows/
      terraform-plan.yml
      terraform-apply.yml

Remote State Backend

Store Terraform state in S3 with DynamoDB locking to prevent concurrent modifications:

# environments/prod/backend.tf
terraform {
  backend "s3" {
    bucket         = "my-terraform-state"
    key            = "ceph/prod/terraform.tfstate"
    region         = "us-east-1"
    encrypt        = true
    dynamodb_table = "terraform-state-lock"
  }
}

Reusable Ceph Pool Module

# modules/ceph-pool/main.tf
resource "kubernetes_manifest" "pool" {
  manifest = {
    apiVersion = "ceph.rook.io/v1"
    kind       = "CephBlockPool"
    metadata = {
      name      = var.pool_name
      namespace = var.namespace
    }
    spec = {
      failureDomain = var.failure_domain
      replicated = {
        size                   = var.replica_size
        requireSafeReplicaSize = true
      }
    }
  }
}

# modules/ceph-pool/variables.tf
variable "pool_name" { type = string }
variable "namespace" { type = string; default = "rook-ceph" }
variable "replica_size" { type = number; default = 3 }
variable "failure_domain" { type = string; default = "host" }

Environment-Specific Configuration

# environments/prod/main.tf
module "rbd_pool" {
  source = "../../modules/ceph-pool"

  pool_name    = "prod-rbd"
  replica_size = 3
}

module "rgw_data_pool" {
  source = "../../modules/ceph-pool"

  pool_name    = "prod-rgw-data"
  replica_size = 3
}
# environments/dev/main.tf
module "rbd_pool" {
  source = "../../modules/ceph-pool"

  pool_name    = "dev-rbd"
  replica_size = 2  # fewer replicas in dev
}

CI/CD Pipeline with GitHub Actions

# .github/workflows/terraform-plan.yml
name: Terraform Plan

on:
  pull_request:
    paths:
      - 'environments/**'
      - 'modules/**'

jobs:
  plan:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        environment: [dev, staging, prod]
    steps:
      - uses: actions/checkout@v4
      - uses: hashicorp/setup-terraform@v3

      - name: Configure AWS credentials
        uses: aws-actions/configure-aws-credentials@v4
        with:
          role-to-assume: ${{ secrets.AWS_ROLE_ARN }}
          aws-region: us-east-1

      - name: Terraform Init
        run: terraform init
        working-directory: environments/${{ matrix.environment }}

      - name: Terraform Plan
        run: terraform plan -out=tfplan
        working-directory: environments/${{ matrix.environment }}
        env:
          KUBECONFIG_DATA: ${{ secrets.KUBECONFIG }}

      - name: Upload Plan
        uses: actions/upload-artifact@v4
        with:
          name: tfplan-${{ matrix.environment }}
          path: environments/${{ matrix.environment }}/tfplan
# .github/workflows/terraform-apply.yml
name: Terraform Apply

on:
  push:
    branches: [main]
    paths:
      - 'environments/**'
      - 'modules/**'

jobs:
  apply:
    runs-on: ubuntu-latest
    environment: production
    steps:
      - uses: actions/checkout@v4
      - uses: hashicorp/setup-terraform@v3

      - name: Configure AWS credentials
        uses: aws-actions/configure-aws-credentials@v4
        with:
          role-to-assume: ${{ secrets.AWS_ROLE_ARN }}
          aws-region: us-east-1

      - name: Terraform Init
        run: terraform init
        working-directory: environments/prod

      - name: Terraform Apply
        run: terraform apply -auto-approve
        working-directory: environments/prod

Drift Detection

# Check for infrastructure drift
terraform plan -detailed-exitcode
# Exit code 0: no changes
# Exit code 1: error
# Exit code 2: changes detected (drift)

# Schedule weekly drift checks via cron
0 9 * * 1 cd /opt/ceph-infra/environments/prod && terraform plan -detailed-exitcode

Summary

Version controlling Ceph infrastructure with Terraform, remote state backends, and GitHub Actions CI/CD creates a safe, reviewable change management workflow. Every Ceph configuration change goes through a plan-review-apply cycle, reducing the risk of accidental modifications and providing a complete audit trail of all infrastructure changes.