Kubeblocks Skills

Legacy compatibility shim for backup workflows. The primary Day-2 entry is kubeblocks-op-backup. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Install the KubeBlocks operator on any Kubernetes cluster via Helm. Handles version selection, environment detection (local dev vs production, China mainland vs global network), image registry configuration, prerequisite checks, and post-install verification. Use when the user asks to install, deploy, or set up KubeBlocks. NOT for upgrading an existing KubeBlocks installation (see KubeBlocks official upgrade docs), uninstalling KubeBlocks (see the Uninstall section in this skill), or creating database clusters after installation (see kubeblocks-create-cluster or kubeblocks-addon-* skills).

Legacy compatibility shim for restore workflows. The primary Day-2 entry is kubeblocks-op-restore. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Primary Day-2 backup entry for KubeBlocks-managed database clusters. Use this for backup workflows on existing clusters. Confirm support in the ops capability matrix when available. The legacy kubeblocks-backup skill remains only as a compatibility shim.

Primary Day-2 expose entry for KubeBlocks-managed database clusters. Use this for service exposure on existing clusters. Confirm support in the ops capability matrix when available. The legacy kubeblocks-expose-service skill remains only as a compatibility shim.

Check whether a Kubernetes environment is ready for first-time KubeBlocks database rollout, then emit an environment profile / recommendation bundle for downstream engine-entry skills. Use this before provisioning MySQL, PostgreSQL, Redis, MongoDB, Kafka, or any other database when rollout readiness is still unknown.

Primary Day-2 restore entry for KubeBlocks-managed database clusters. Use this for restore workflows on existing clusters. Confirm support in the ops capability matrix when available. The legacy kubeblocks-restore skill remains only as a compatibility shim.

Primary Day-2 upgrade entry for KubeBlocks-managed database clusters. Use this for engine upgrade workflows on existing clusters. Confirm support in the ops capability matrix when available. The legacy kubeblocks-minor-version-upgrade skill remains only as a compatibility shim.

Legacy compatibility shim for planned switchover. The primary Day-2 entry is kubeblocks-op-switchover. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Legacy compatibility shim for Kafka provisioning on KubeBlocks. The primary create-time entry is kubeblocks-engine-kafka. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Legacy compatibility shim for MySQL provisioning on KubeBlocks. The primary create-time entry is kubeblocks-engine-mysql. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Legacy compatibility shim for Redis provisioning on KubeBlocks. The primary create-time entry is kubeblocks-engine-redis. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Primary create-time entry for TiDB on KubeBlocks. Use when the user wants to provision TiDB and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown.

Legacy compatibility shim for Milvus provisioning on KubeBlocks. The primary create-time entry is kubeblocks-engine-milvus. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Legacy compatibility shim for Qdrant provisioning on KubeBlocks. The primary create-time entry is kubeblocks-engine-qdrant. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Primary create-time entry for Kafka on KubeBlocks. Use when the user wants to provision Kafka and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown. The legacy kubeblocks-addon-kafka skill remains only as a compatibility shim.

Primary create-time entry for MinIO on KubeBlocks. Use when the user wants to provision MinIO and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown.

Primary create-time entry for MySQL on KubeBlocks. Use when the user wants to provision MySQL and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown. The legacy kubeblocks-addon-mysql skill remains only as a compatibility shim.

Primary create-time entry for Redis on KubeBlocks. Use when the user wants to provision Redis and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown. The legacy kubeblocks-addon-redis skill remains only as a compatibility shim.

Primary Day-2 lifecycle entry for KubeBlocks-managed database clusters. Use this for stop, start, and restart on existing clusters. Confirm support in the ops capability matrix when available. The legacy kubeblocks-cluster-lifecycle skill remains only as a compatibility shim.

Legacy compatibility shim for MongoDB provisioning on KubeBlocks. The primary create-time entry is kubeblocks-engine-mongodb. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Access-security capability entry for TLS and mTLS on existing KubeBlocks clusters. Use when the user wants to enable, verify, or rotate encrypted database connections. Do not use this as a create-time primary entry; create-time routing still starts at preflight plus the dedicated engine skill.

Primary create-time entry for Milvus on KubeBlocks. Use when the user wants to provision Milvus and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown. The legacy kubeblocks-addon-milvus skill remains only as a compatibility shim.

Primary create-time entry for Pulsar on KubeBlocks. Use when the user wants to provision Pulsar and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown.

Primary create-time entry for Qdrant on KubeBlocks. Use when the user wants to provision Qdrant and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown. The legacy kubeblocks-addon-qdrant skill remains only as a compatibility shim.

Primary Day-2 switchover entry for KubeBlocks-managed database clusters. Use this for planned primary-secondary switchovers on existing clusters. Confirm support in the ops capability matrix when available. The legacy kubeblocks-switchover skill remains only as a compatibility shim.

Legacy compatibility shim for RabbitMQ provisioning on KubeBlocks. The primary create-time entry is kubeblocks-engine-rabbitmq. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Legacy compatibility shim for the generic KubeBlocks create path. The primary create-time fallback is now kubeblocks-engine-generic. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Destructive lifecycle capability entry for removing an existing KubeBlocks cluster. Use when the user wants to decommission a database cluster and has explicitly confirmed the data-protection boundary. Do not confuse this with stop/start lifecycle actions or operator uninstall.

Generic create-time fallback for KubeBlocks engines that do not yet have a dedicated kubeblocks-engine-* entry. Use this only after kubeblocks-preflight and only when the engine is not locked into the Tier-1 dedicated set. The legacy kubeblocks-create-cluster skill remains only as a compatibility shim.

Primary create-time entry for MariaDB on KubeBlocks. Use when the user wants to provision MariaDB and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown.

Primary create-time entry for MongoDB on KubeBlocks. Use when the user wants to provision MongoDB and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown. The legacy kubeblocks-addon-mongodb skill remains only as a compatibility shim.

Legacy compatibility shim for service exposure. The primary Day-2 entry is kubeblocks-op-expose. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Primary Day-2 reconfigure entry for KubeBlocks-managed database clusters. Use this for parameter and configuration changes on existing clusters. Confirm support in the ops capability matrix when available. The legacy kubeblocks-reconfigure-parameters skill remains only as a compatibility shim.

Primary create-time entry for RabbitMQ on KubeBlocks. Use when the user wants to provision RabbitMQ and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown. The legacy kubeblocks-addon-rabbitmq skill remains only as a compatibility shim.

Access-security capability entry for account, password, and credential handling on existing KubeBlocks clusters. Use when the user wants to retrieve, rotate, reset, or preconfigure database credentials. Do not use this as a create-time primary entry; create-time routing still starts at preflight plus the dedicated engine skill.

Recovery capability entry for replica repair via RebuildInstance on existing KubeBlocks clusters. Use when a secondary is unrecoverable and normal failover is insufficient. Do not use this as a create-time entry or as a substitute for planned switchover or full restore.

Legacy compatibility shim for PostgreSQL provisioning on KubeBlocks. The primary create-time entry is kubeblocks-engine-postgresql. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Compatibility shim for KubeBlocks observability. Use this when the user broadly asks to "set up monitoring"; this skill decides whether to integrate with an existing stack or bootstrap a new one.

Legacy compatibility shim for vertical scaling. The primary Day-2 entry is kubeblocks-op-vertical-scale. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Legacy compatibility shim for volume expansion. The primary Day-2 entry is kubeblocks-op-volume-expansion. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Legacy compatibility shim for cluster lifecycle actions. The primary Day-2 entry is kubeblocks-op-lifecycle. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Primary create-time entry for ClickHouse on KubeBlocks. Use when the user wants to provision ClickHouse and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown.

Primary create-time entry for OpenSearch on KubeBlocks. Use when the user wants to provision OpenSearch and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown.

Primary create-time entry for PostgreSQL on KubeBlocks. Use when the user wants to provision PostgreSQL and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown. The legacy kubeblocks-addon-postgresql skill remains only as a compatibility shim.

Primary Day-2 vertical scale entry for KubeBlocks-managed database clusters. Use this for CPU and memory changes on existing clusters. Confirm support in the ops capability matrix when available. The legacy kubeblocks-vertical-scaling skill remains only as a compatibility shim.

Legacy compatibility shim for horizontal scaling. The primary Day-2 entry is kubeblocks-op-horizontal-scale. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Legacy compatibility shim for Elasticsearch provisioning on KubeBlocks. The primary create-time entry is kubeblocks-engine-elasticsearch. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Primary Day-2 horizontal scale entry for KubeBlocks-managed database clusters. Use this for replica or shard count changes on existing clusters. Confirm support in the ops capability matrix when available. The legacy kubeblocks-horizontal-scaling skill remains only as a compatibility shim.

Primary Day-2 volume expansion entry for KubeBlocks-managed database clusters. Use this for storage growth on existing clusters. Confirm support in the ops capability matrix when available. The legacy kubeblocks-volume-expansion skill remains only as a compatibility shim.

Primary create-time entry for Elasticsearch on KubeBlocks. Use when the user wants to provision Elasticsearch and needs the correct topology, version, storage, sizing, connection, and next-hop guidance. Run kubeblocks-preflight first when environment readiness is unknown. The legacy kubeblocks-addon-elasticsearch skill remains only as a compatibility shim.

Primary observability entry for KubeBlocks-managed databases. Use this when the user broadly asks for monitoring or observability and you need to choose between integrating with an existing stack, bootstrapping a new stack, or declaring the current readiness level. The legacy kubeblocks-setup-monitoring skill remains only as a compatibility shim.

Legacy compatibility shim for engine upgrade workflows. The primary Day-2 entry is kubeblocks-op-upgrade. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Legacy compatibility shim for parameter reconfiguration. The primary Day-2 entry is kubeblocks-op-reconfigure. Keep this skill callable for older references, but do not recommend it as the main path for cold-start agents.

Integrate KubeBlocks database metrics into an existing Prometheus / Grafana stack. Use this when the monitoring base already exists and the remaining work is scrape configuration, dashboards, and alerting readiness.

Bootstrap a Prometheus / Grafana monitoring stack for KubeBlocks database metrics when no usable observability base exists yet.