KubeBlocks
BlogsEnterprise
⌘K
​
Blogs

Overview
Quickstart
Architecture

Operations

Stop / Start / Restart
Vertical Scaling
Horizontal Scaling
Volume Expansion
Reconfigure
Manage Services

Observability

Prometheus Integration
  1. Prerequisites
  2. Expand the Broker Volume
  3. Cleanup

Volume Expansion for RocketMQ

Volume expansion increases the storage allocated to broker pods. The underlying StorageClass must support volume expansion.

Prerequisites

    Before proceeding, verify your environment meets these requirements:

    • A functional Kubernetes cluster (v1.21+ recommended)
    • kubectl v1.21+ installed and configured with cluster access
    • Helm installed (installation guide)
    • KubeBlocks installed (installation guide)
    • RocketMQ Add-on installed and a RocketMQ cluster running (see Quickstart)
    NOTE

    Volume expansion requires a StorageClass with allowVolumeExpansion: true. Verify this before proceeding:

    kubectl get storageclass

    Expand the Broker Volume

    The broker data PVC stores message logs. Use the sharding group name broker to expand from 10Gi to 20Gi:

    kubectl apply -f - <<EOF apiVersion: operations.kubeblocks.io/v1alpha1 kind: OpsRequest metadata: name: rocketmq-volumeexpansion namespace: demo spec: clusterName: rocketmq-cluster type: VolumeExpansion volumeExpansion: - componentName: broker volumeClaimTemplates: - name: data storage: 20Gi EOF

    Monitor progress:

    kubectl get opsrequest rocketmq-volumeexpansion -n demo -w
    Example Output
    NAME TYPE CLUSTER STATUS PROGRESS AGE rocketmq-volumeexpansion VolumeExpansion rocketmq-cluster Succeed 1/1 60s

    Verify the new storage size:

    kubectl get pvc -n demo -l app.kubernetes.io/instance=rocketmq-cluster
    Example Output
    NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE data-rocketmq-cluster-broker-t9j-0 Bound ... 20Gi RWO standard 10m

    Cleanup

    kubectl delete opsrequest rocketmq-volumeexpansion -n demo --ignore-not-found

    © 2026 KUBEBLOCKS INC