kubeblocks-restore

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Legacy compatibility shim that provides a backward-compatible restore entry point, delegating to the primary restore workflow to preserve continuity for day-2 operations.

Core Features & Use Cases

  • Provides a backward-compatible entry point for restore workflows, enabling legacy references to trigger the primary kubeblocks-op-restore path.
  • Supports full restore and PITR workflows by routing requests to the main engine while keeping the original skill as a reference.
  • Ideal for environments with existing automation or documentation that reference kubeblocks-restore, ensuring stability during migrations.

Quick Start

To begin a restore, reference the legacy kubeblocks-restore workflow and proceed with the primary kubeblocks-op-restore path for day-2 operations.

Frequently Asked Questions about kubeblocks-restore

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

FAQPage Schema
How do I restore a KubeBlocks database cluster from a backup?

Restoring a KubeBlocks database cluster involves referencing the restore workflow, which delegates to the primary restore engine to safely recover data and execute day-2 operations.

What is the kubeblocks-restore workflow used for?

The kubeblocks-restore workflow acts as a legacy compatibility shim, providing a backward-compatible entry point that delegates restore operations to the primary engine for day-2 operations.

Can I perform PITR and full restores using the KubeBlocks restore compatibility path?

Yes, the KubeBlocks restore compatibility path supports both full restore and PITR workflows by routing requests to the main engine while keeping the original skill as a reference.

Does the KubeBlocks legacy restore entry point support existing automation references?

Yes, the legacy restore entry point is designed for environments with existing automation or documentation referencing kubeblocks-restore, ensuring stability and continuity during migrations.

Why should I use the legacy kubeblocks-restore entry instead of the main restore path?

Use the legacy kubeblocks-restore entry to preserve continuity for existing references and compatibility tests, while the main path remains kubeblocks-op-restore for direct restore operations.