kubeblocks-op-upgrade

Automate Day-2 engine upgrades for KubeBlocks clusters with capability-matrix validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Primary Day-2 upgrade entry to manage engine upgrades on existing KubeBlocks clusters, with explicit checks against the ops capability matrix and clear routing to observability or troubleshooting when needed.

Core Features & Use Cases

  • Engine upgrade orchestration: coordinates cluster identification, engine version, and upgrade path for existing deployments.
  • Capability-matrix-driven gating: validates support before actions, propagates explicit unsupported/partial outcomes.
  • Observability & Troubleshooting routing: redirects to observability router or troubleshooting skill as appropriate.

Quick Start

Initiate an engine upgrade on an existing KubeBlocks cluster and verify support in the ops capability matrix before proceeding.

Frequently Asked Questions about kubeblocks-op-upgrade

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

FAQPage Schema
How do I upgrade the database engine on an existing KubeBlocks cluster?

The KubeBlocks upgrade workflow validates engine compatibility against the ops capability matrix before applying upgrades, explicitly propagating unsupported or partial support outcomes to prevent incompatible engine version changes on existing clusters.

How does the ops capability matrix check work during a KubeBlocks upgrade?

The ops capability matrix acts as a gating mechanism during KubeBlocks upgrades by validating support for the target engine version before any action is taken. It explicitly propagates unsupported or partial support outcomes to prevent incompatible upgrades.

What is the process for troubleshooting a failed KubeBlocks cluster upgrade?

The KubeBlocks upgrade workflow routes troubleshooting requests to the dedicated kubeblocks-troubleshoot path to diagnose and resolve engine version compatibility or deployment issues encountered during the Day-2 upgrade process.

Can I monitor KubeBlocks engine upgrade progress through observability routing?

Yes, the KubeBlocks upgrade workflow explicitly redirects observability requests to the kubeblocks-observability-router, enabling you to monitor engine upgrade progress, track cluster status, and verify deployment health metrics during Day-2 operations.

Do I need the ops capability matrix YAML to perform a KubeBlocks Day-2 upgrade?

Yes, accessing the predefined ops-capability-matrix YAML is required to perform a KubeBlocks Day-2 upgrade. The upgrade workflow depends on this file to validate engine compatibility and gate upgrade actions before applying changes to existing clusters.