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

kubeblocks-addon-mysql

Expose a legacy MySQL provisioning entry path for KubeBlocks compatibility.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Legacy compatibility shim ensures older MySQL provisioning references continue to work with KubeBlocks, avoiding breakages when the primary engine path evolves.

Core Features & Use Cases

  • Provides a stable, secondary entry point for MySQL provisioning to support legacy tooling.
  • Documented prerequisites and workflow alignment with the primary kubeblocks-engine-mysql path.
  • Use Case: Operators upgrading to the latest engine can keep integrations calling the legacy path without disruption.

Quick Start

Initialize the legacy shim to invoke provisioning workflows via the legacy entry point, while the primary path remains kubeblocks-engine-mysql.

Frequently Asked Questions about kubeblocks-addon-mysql

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

FAQPage Schema
How do I maintain legacy MySQL provisioning on Kubernetes when upgrading KubeBlocks?▼

To maintain legacy MySQL provisioning on Kubernetes, use this shim to expose a legacy entry path. It ensures older references resolve correctly while the primary creation flow uses the kubeblocks-engine-mysql path.

What is a legacy provisioning shim in KubeBlocks?▼

A legacy provisioning shim in KubeBlocks is a secondary entry point for MySQL provisioning. It ensures older references continue to work without disruption, avoiding breakages when the primary engine path evolves.

Does the KubeBlocks legacy MySQL shim work alongside the primary engine?▼

Yes, the KubeBlocks legacy MySQL shim enforces coexistence with the primary kubeblocks-engine-mysql entry. It maintains documented prerequisites and workflow alignment while supporting legacy tooling.

Why do I need a legacy entry path for MySQL provisioning?▼

You need a legacy entry path for MySQL provisioning to prevent integration breakages. Operators upgrading to the latest KubeBlocks engine can keep existing tooling calling the legacy path without disruption.

How to initialize MySQL provisioning via the legacy KubeBlocks entry point?▼

To initialize MySQL provisioning via the legacy KubeBlocks entry point, invoke the shim's workflows. The primary path remains kubeblocks-engine-mysql, while older references resolve through this secondary entry.

Related Skills

Explore More Software Engineering Skills→
apecloudapecloud
3

kubeblocks-addon-milvus

Route legacy Milvus provisioning requests to kubeblocks-engine-milvus on KubeBlocks.

Official
Basic
apecloudapecloud
3

kubeblocks-addon-kafka

Route legacy Kafka provisioning requests to kubeblocks-engine-kafka.

Official
Intermediate
apecloudapecloud
3

kubeblocks-addon-rabbitmq

Provides legacy RabbitMQ provisioning compatibility shim for KubeBlocks.

Official
Basic
rnavarychrnavarych
14

role-database:database-devops

Automate database provisioning, Kubernetes deployment, and CI/CD integration with Terraform.

Community
Advanced