kubeblocks-op-restore

Automate Day-2 restore workflows for KubeBlocks-managed database clusters.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Restore workflows for existing KubeBlocks-managed database clusters, enabling Day-2 recovery with guided decision-making and safe rollback boundaries.

Core Features & Use Cases

  • Day-2 restore orchestration: coordinates cluster identification, engine targeting, and restore actions with policy checks.
  • Safety and governance: ensures explicit support in the ops capability matrix before acting and routes monitoring to observability and troubleshooting components.
  • Use Case: recover a failed cluster by applying a known-good snapshot and validating post-restore health.

Quick Start

Provide the target cluster and the desired restore point to begin the restore process.

Frequently Asked Questions about kubeblocks-op-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 snapshot?▼

To restore a KubeBlocks database cluster, provide the target cluster name and desired restore point. The restore workflow then coordinates cluster identification, engine targeting, and policy checks to safely recover the database.

Can I restore an existing KubeBlocks cluster across different database engines?▼

Yes, restore workflows apply to existing KubeBlocks-managed database clusters across engines. The process guides you through engine targeting and policy checks to ensure the restore action is explicitly supported.

What safety checks are enforced during a KubeBlocks Day-2 restore operation?▼

KubeBlocks restore operations enforce safety and governance by checking the ops capability matrix for explicit support, routing monitoring to observability components, and validating post-restore health with safe rollback boundaries.

What do I need to provide to start a database cluster restore workflow?▼

You need to provide the target cluster identifier and the desired restore point to begin the restore process. The workflow then applies these inputs to automate the Day-2 recovery actions.

Does KubeBlocks validate cluster health after applying a restore?▼

Yes, the restore workflow validates post-restore health by routing monitoring checks to observability and troubleshooting components. This ensures the recovered database cluster operates normally after the snapshot is applied.

When should I avoid using the KubeBlocks restore workflow for cluster recovery?▼

You should avoid initiating a restore if the ops capability matrix does not explicitly support the restore scenario for your specific cluster engine. The workflow enforces these explicit support decisions before taking action.