kubeblocks-volume-expansion

Guide Kubernetes volume expansion in KubeBlocks clusters with OpsRequest templates.

3|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-volume-expansion
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kubeblocks-volume-expansion
Source: https://github.com/apecloud/kubeblocks-skills/tree/main/skills/kubeblocks-volume-expansion
Command: npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-volume-expansion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Volume expansion workflows in KubeBlocks can suffer from parity gaps and legacy references. This Skill provides a legacy compatibility shim so cold-start agents can reuse established volume-expansion patterns while guiding them toward the primary kubeblocks-op-volume-expansion path.

Core Features & Use Cases

  • Backward-compatibility shim for volume expansion, keeping legacy references functional while steering to the main entry.
  • Includes safe, templated OpsRequest guidance and pre-checks to verify StorageClass support and cluster health.
  • Use case: migrating from a legacy volume-expansion path to the canonical kubeblocks-op-volume-expansion workflow with minimal disruption.

Quick Start

Follow the primary path kubeblocks-op-volume-expansion for active expansions, using this shim only for legacy references and context.

Frequently Asked Questions about kubeblocks-volume-expansion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I expand Kubernetes volumes in KubeBlocks safely?

Volume expansion in KubeBlocks requires a StorageClass that supports resizing, a healthy cluster state, and no pending OpsRequests. You apply a validated OpsRequest template to resize volumes safely without disrupting online workloads.

What are the prerequisites for Kubernetes volume expansion in KubeBlocks?

Volume expansion requires a StorageClass that supports resizing, a healthy cluster state, and no pending OpsRequests. You must validate these conditions before applying an OpsRequest template to perform online resizing.

Can I dry-run a volume expansion OpsRequest in Kubernetes?

Yes, KubeBlocks volume expansion guidance provides YAML OpsRequest templates configured for dry-run validation, letting you verify the resize operation safely before applying it to a live cluster.

Why is my KubeBlocks volume expansion not working?

Volume expansion fails when the StorageClass lacks resize support, the cluster is unhealthy, or pending OpsRequests block new operations. You must run pre-checks to confirm StorageClass compatibility and cluster health before applying.

How do I migrate from legacy KubeBlocks volume expansion to the canonical path?

You use a backward-compatibility shim to keep legacy volume expansion references functional while steering cold-start agents toward the primary kubeblocks-op-volume-expansion workflow, ensuring minimal disruption during migration.