# Kubeblocks Op Volume Expansion

> Primary Day-2 volume expansion entry for KubeBlocks-managed database clusters. Use this for storage growth on existing clusters. Confirm support in the ops capability matrix when available. The legacy kubeblocks-volume-expansion skill remains only as a compatibility shim.

- Skill: `apecloud/kubeblocks-op-volume-expansion` (Agent Skill)
- Install (CLI): `npx skillmds@latest add apecloud/kubeblocks-op-volume-expansion`
- Raw SKILL.md: https://api.skillmd.com/api/skills/apecloud/kubeblocks-op-volume-expansion/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: apecloud (https://skillmd.com/u/apecloud)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/apecloud/kubeblocks-op-volume-expansion

---


# Volume Expansion Ops Entry

Use this as the primary Day-2 entry for storage growth on existing clusters.

## Entry Contract

- Confirm support in [ops-capability-matrix](../../references/coverage/ops-capability-matrix.yaml) before acting.
- Keep create-time provisioning questions on the engine-entry side.
- If support is `unsupported` or `partial`, say that explicitly before you act.
- Route monitoring asks to [kubeblocks-observability-router](../kubeblocks-observability-router/SKILL.md) and broken-state diagnosis to [kubeblocks-troubleshoot](../kubeblocks-troubleshoot/SKILL.md).

## Day-2 Checklist

1. Identify the cluster, engine, and requested action.
2. Confirm the matrix row for that engine and capability.
3. Follow the preserved detailed workflow below when the capability is supported.
4. Verify post-change health and capture the rollback boundary.

## Preserved Detailed Reference

For preserved OpsRequest examples and older command snippets, see [legacy reference](../kubeblocks-volume-expansion/references/reference.md).
Do not recommend [kubeblocks-volume-expansion](../kubeblocks-volume-expansion/SKILL.md) as the primary entry once this `kubeblocks-op-*` entry exists.