skills.rest
apecloud
apecloudOFFICIAL
Explore all skills by this author →
WebsiteGitHub

kubeblocks-cluster-lifecycle

Delegates Kubeblocks cluster lifecycle tasks from legacy to current engine.

3|Updated Mar 12, 2026
Search Tags:#routing#compatibility#lifecycle#legacy#cluster#operator#kubeblocks
One-click install
npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-cluster-lifecycle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: kubeblocks-cluster-lifecycle
Source: https://github.com/apecloud/kubeblocks-skills/tree/main/skills/kubeblocks-cluster-lifecycle
Command: npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-cluster-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Legacy cluster lifecycle routing addresses backward compatibility, ensuring older references to cluster lifecycle actions continue to function while the actual work is performed by the primary engine.

Core Features & Use Cases

  • Preserves the legacy entry point kubeblocks-cluster-lifecycle for compatibility
  • Delegates execution to kubeblocks-op-lifecycle for Day-2 operations
  • Maintains a stable, documented path for automation scripts and operators during cluster lifecycle tasks.

Quick Start

Use kubeblocks-cluster-lifecycle only for legacy references; for standard Day-2 operations, use kubeblocks-op-lifecycle.

Frequently Asked Questions about kubeblocks-cluster-lifecycle

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

FAQPage Schema
How do I maintain legacy cluster lifecycle compatibility in KubeBlocks operators?▼

Legacy cluster lifecycle compatibility is maintained by preserving the old entry point and rerouting execution to the primary engine. This ensures older references to Day-2 operations continue functioning without breaking existing automation scripts.

What does the legacy cluster lifecycle routing process do during Day-2 operations?▼

The legacy cluster lifecycle routing process delegates Day-2 operations to the primary lifecycle engine. It acts as a compatibility bridge, taking legacy references and forwarding the actual execution to the main operator workflow.

Can I use standard Day-2 operations directly instead of routing through the legacy cluster lifecycle entry point?▼

Yes, for standard Day-2 operations you should use the primary lifecycle engine directly. The legacy cluster lifecycle entry point exists solely for backward compatibility with older automation scripts and operators.

When should I use the legacy cluster lifecycle routing instead of the primary engine?▼

Use the legacy cluster lifecycle routing only when maintaining older references that require backward compatibility. If you are building new automation scripts or operators, invoke the primary lifecycle engine directly for Day-2 operations.

Does routing legacy cluster lifecycle actions to the main engine affect runtime safety?▼

Routing legacy cluster lifecycle actions to the main engine meets runtime safety and compatibility requirements. It preserves the old entry point while delegating execution, ensuring stable operation without compromising the primary workflow.

Why are my legacy KubeBlocks cluster lifecycle scripts still working after an engine upgrade?▼

Legacy KubeBlocks cluster lifecycle scripts continue working because the old entry point is preserved for backward compatibility. Execution is rerouted to the primary engine, ensuring older references function correctly during Day-2 operations.

Related Skills

Explore More Software Engineering Skills→
apecloudapecloud
3

kubeblocks-op-lifecycle

Automate Day-2 stop, start, and restart operations for KubeBlocks-managed database clusters.

Official
Intermediate
kcns008kcns008
3

kubernetes-operations

Automate Kubernetes and OpenShift cluster upgrades, backups, node management, and monitoring.

Community
Advanced
apecloudapecloud
3

kubeblocks-restore

Route legacy restore requests to the primary kubeblocks-op-restore workflow.

Official
Basic
nghiahsgsnghiahsgs
32

taw-deploy

Forward deployment commands to the main /taw workflow.

Community
Basic