kubeblocks-horizontal-scaling

Name: kubeblocks-horizontal-scaling
Availability: InStock
Author: ApeCloud

Route legacy horizontal-scaling requests to the primary kubeblocks workflow.

3|Updated Mar 12, 2026

Search Tags:#workflow #routing #compatibility #kubernetes #cluster-management #horizontal-scaling #kubeblocks

Ready to run

npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-horizontal-scaling

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kubeblocks-horizontal-scaling
Source: https://github.com/apecloud/kubeblocks-skills/tree/main/skills/kubeblocks-horizontal-scaling
Command: npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-horizontal-scaling

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Legacy compatibility shim provides a safeguard by exposing the legacy horizontal-scaling entry while delegating real execution to the primary kubeblocks-op-horizontal-scale workflow. This ensures older references remain functional during transitions and upgrades.

Core Features & Use Cases

Keeps the old kubeblocks-horizontal-scaling entry callable for compatibility.
Documents the common horizontal-scaling workflow and how to migrate to the primary entry.
Serves as a reference during maintenance, onboarding, and transition periods for cluster scaling tasks.

Quick Start

Call this skill to view the legacy horizontal-scaling workflow and then transition to the primary entry kubeblocks-op-horizontal-scale.

Frequently Asked Questions about kubeblocks-horizontal-scaling

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

FAQPage Schema

How do I handle legacy kubeblocks horizontal-scaling requests during a Kubernetes cluster migration?▼

Legacy kubeblocks horizontal-scaling requests are routed to the primary kubeblocks-op-horizontal-scale workflow via a compatibility shim, preserving older entry points while delegating real execution to ensure safe transitions.

When do I need a compatibility shim for horizontal scaling workflows in Kubernetes?▼

You need a compatibility shim for horizontal scaling when your environment still references the legacy kubeblocks-horizontal-scaling entry and you are migrating to kubeblocks-op-horizontal-scale for MySQL, PostgreSQL, Redis, MongoDB, and related components.

Does the kubeblocks-horizontal-scaling entry still work for MongoDB and Redis cluster management?▼

Yes, the kubeblocks-horizontal-scaling entry remains callable for MongoDB and Redis cluster management, acting as a legacy reference that delegates execution to the primary kubeblocks-op-horizontal-scale workflow without runtime dependency on older paths.

What is the best way to transition from legacy horizontal scaling to the primary kubeblocks workflow?▼

The best way to transition is to call the legacy kubeblocks-horizontal-scaling skill to view the documented workflow, pre-checks, and monitoring steps, then route your scaling operations to the primary kubeblocks-op-horizontal-scale entry.

Are there dependencies required to use the kubeblocks horizontal scaling compatibility routing?▼

No runtime dependencies on older paths are required to use the kubeblocks horizontal scaling compatibility routing, as the shim safely delegates execution to the primary kubeblocks-op-horizontal-scale workflow during your migration period.

Why does my kubeblocks horizontal scaling workflow reference older entry points during maintenance?▼

Your kubeblocks horizontal scaling workflow references older entry points because the legacy shim exposes them for compatibility, serving as a reference during maintenance, onboarding, and transition periods for cluster scaling tasks.