Kubeblocks Op Vertical Scale

Primary Day-2 vertical scale entry for KubeBlocks-managed database clusters. Use this for CPU and memory changes on existing clusters. Confirm support in the ops capability matrix when available. The legacy kubeblocks-vertical-scaling skill remains only as a compatibility shim.

apecloud Updated

File contents

Vertical Scale Ops Entry

Use this as the primary Day-2 entry for CPU and memory changes on existing clusters.

Entry Contract

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. Do not recommend kubeblocks-vertical-scaling as the primary entry once this kubeblocks-op-* entry exists.

apecloud/kubeblocks-skills/tree/main/skills/kubeblocks-op-vertical-scale commit 187944484a

Frequently asked questions

npx skillmds@latest add apecloud/kubeblocks-op-vertical-scale