apecloud 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 before acting.
- Keep create-time provisioning questions on the engine-entry side.
- If support is
unsupportedorpartial, say that explicitly before you act. - Route monitoring asks to kubeblocks-observability-router and broken-state diagnosis to kubeblocks-troubleshoot.
Day-2 Checklist
- Identify the cluster, engine, and requested action.
- Confirm the matrix row for that engine and capability.
- Follow the preserved detailed workflow below when the capability is supported.
- Verify post-change health and capture the rollback boundary.
Preserved Detailed Reference
For preserved OpsRequest examples and older command snippets, see legacy reference.
Do not recommend kubeblocks-volume-expansion as the primary entry once this kubeblocks-op-* entry exists.