kubeblocks-vertical-scaling

Route legacy kubeblocks-vertical-scaling calls to kubeblocks-op-vertical-scale.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preserves backward-compatible vertical-scaling workflows for KubeBlocks clusters by routing legacy references to the supported Day-2 entry point kubeblocks-op-vertical-scale, enabling teams to transition without breaking automation.

Core Features & Use Cases

  • Backward compatibility: Keeps using the older kubeblocks-vertical-scaling path while you migrate to the primary entry.
  • Safe transition guidance: Provides a clear path toward kubeblocks-op-vertical-scale and minimizes downtime during cutovers.
  • Use Case: An operator updating a cluster’s resources can still invoke the legacy workflow and progressively adopt the modern entry.

Quick Start

Use this legacy skill to access vertical scaling workflows via the older entry point while transitioning to the primary kubeblocks-op-vertical-scale.

Frequently Asked Questions about kubeblocks-vertical-scaling

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

FAQPage Schema
How do I keep using the legacy kubeblocks-vertical-scaling workflow without breaking my automation?

Legacy kubeblocks-vertical-scaling workflows remain functional by routing references to the primary kubeblocks-op-vertical-scale entry point, allowing teams to progressively migrate without breaking existing automation.

What is vertical scaling in KubeBlocks and when do I need it?

Vertical scaling in KubeBlocks adjusts cluster resource allocations during Day-2 operations, needed when updating CPU or memory limits to meet changing workload demands.

Can I still invoke the older kubeblocks-vertical-scaling path while transitioning to the modern entry?

Yes, the legacy kubeblocks-vertical-scaling path remains accessible and routes to kubeblocks-op-vertical-scale, allowing operators to invoke older workflows while progressively adopting the modern entry point.

What is the best way to migrate from legacy KubeBlocks vertical scaling to the supported Day-2 entry point?

The best way to migrate is using the backward-compatible legacy path that safely routes to kubeblocks-op-vertical-scale, minimizing downtime during cutovers while maintaining documentation fidelity and workflow continuity.

Are there limitations to using the legacy kubeblocks-vertical-scaling workflow for cluster resource updates?

The legacy kubeblocks-vertical-scaling workflow is a transitional compatibility layer; while functional, it guides users toward the primary kubeblocks-op-vertical-scale entry and should not serve as a permanent solution.

Does KubeBlocks support backward compatibility for older vertical scaling operations?

Yes, KubeBlocks supports backward compatibility for vertical scaling by preserving legacy workflow references and routing them to the current kubeblocks-op-vertical-scale entry point for safe migration.