kubeblocks-engine-mariadb

Provision MariaDB deployments on KubeBlocks with topology and version guidance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a dedicated create-time entry for MariaDB on KubeBlocks, ensuring the correct topology, version, sizing, storage, and next-hop guidance while guiding environment readiness checks.

Core Features & Use Cases

  • Topology and version guidance for MariaDB deployments with clear defaults and restrictions (standalone as the current safe default).
  • Preflight-driven validation to ensure the environment is profiled before create-time actions.
  • Explicit next-hop routing to capability layers such as observability, security, and troubleshooting, with forbidden routes clearly documented.

Quick Start

Run kubeblocks-preflight if the environment is not profiled, then draft a minimal MariaDB cluster manifest using the default topology and serviceVersion guidance.

Frequently Asked Questions about kubeblocks-engine-mariadb

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

FAQPage Schema
How do I deploy MariaDB on Kubernetes with the correct topology?

To deploy MariaDB on Kubernetes, use a topology-aware create-time entry that provisions the deployment with correct topology, version, and storage. Standalone is the current safe default topology.

What is the preflight check for MariaDB deployment on Kubernetes?

Preflight validation profiles your Kubernetes environment to verify readiness before applying any MariaDB create-time workflow. You must run kubeblocks-preflight if the environment is not already profiled.

Can I use a replicated topology instead of standalone for MariaDB in KubeBlocks?

Currently, standalone is the enforced safe default topology for MariaDB in KubeBlocks. The create-time entry enforces engine constraints and restricts forbidden routes.

What should I do after provisioning a MariaDB cluster on Kubernetes?

After provisioning a MariaDB cluster, follow explicit next-hop routing to capability layers such as observability, security, and troubleshooting to manage your deployment.

Are there forbidden routes when creating a MariaDB deployment?

Yes, the MariaDB create-time entry clearly documents forbidden routes and enforces engine constraints to prevent invalid actions, directing you only to proper capability layers.