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

kubeblocks-engine-generic

Deploy generic KubeBlocks engines using kubectl dry-run validation and cluster verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generic create-time fallback for KubeBlocks engines that do not yet have a dedicated kubeblocks-engine-* entry, enabling safe deployments after preflight and before Tier-1 routing.

Core Features & Use Cases

  • Defines explicit input requirements: clusterDef, topology, serviceVersion, storageClassName, sizing, and a connection/verification plan.
  • Provides a repeatable workflow to populate a generic cluster template, validate with kubectl dry-run, then apply and verify the cluster reaches Running.
  • Serves as a compatibility shim for legacy create-cluster scenarios when no dedicated engine exists.

Quick Start

Initiate the generic engine flow after kubeblocks-preflight has selected a non-tier-1 engine and supply clusterDef, topology, and version details.

Frequently Asked Questions about kubeblocks-engine-generic

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

FAQPage Schema
How do I deploy a KubeBlocks cluster when no dedicated engine entry exists?▼

To deploy a KubeBlocks cluster without a dedicated engine, use the generic engine fallback path to populate a cluster template, validate it with kubectl dry-run, apply it, and confirm the cluster reaches Running.

What inputs are required for a generic KubeBlocks engine deployment?▼

A generic KubeBlocks engine deployment requires clusterDef, topology, serviceVersion, storageClassName, sizing, and a connection verification plan to populate the cluster template correctly.

When should I use the generic engine path for a KubeBlocks deployment?▼

Use the generic engine path for a KubeBlocks deployment after preflight identifies a non-tier-1 engine or for legacy create-cluster scenarios lacking a dedicated engine entry.

How do I verify a generic KubeBlocks cluster deployment?▼

To verify a generic KubeBlocks cluster deployment, validate the populated template using kubectl dry-run, apply the configuration, and confirm the cluster status reaches Running.

Does kubeblocks-preflight need to run before the generic engine deployment?▼

Yes, kubeblocks-preflight must run first to select a non-tier-1 engine, which then triggers the generic engine flow to handle the cluster deployment safely.

Can I use the generic KubeBlocks engine path for tier-1 engine deployments?▼

No, the generic KubeBlocks engine path is a fallback for non-tier-1 engines. Tier-1 engines should utilize their dedicated engine entries for deployment routing.

Related Skills

Explore More Software Engineering Skills→
apecloudapecloud
3

kubeblocks-engine-minio

Provision MinIO clusters on KubeBlocks with topology, storage, and preflight validation.

Official
Advanced
apecloudapecloud
3

kubeblocks-create-cluster

Route legacy kubeblocks-create-cluster requests to kubeblocks-engine-generic.

Official
Basic
Matchpoint-AIMatchpoint-AI

terraform-state-recovery

Identify and remove orphaned Kubernetes and Helm resources from Terraform state.

Official
Advanced
apecloudapecloud
3

kubeblocks-addon-redis

Route legacy Redis provisioning requests to a compatibility shim in KubeBlocks.

Official
Basic