apecloud

Route database work on Kubernetes to the right KubeBlocks skill. Use this as the top-level entrypoint when the user needs a database, database operations, or database observability on Kubernetes. The root skill only decides the next hop; detailed workflows live in the leaf skills.

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 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 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 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 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 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 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.

GitHub repository automation: PR label, PR size label, PR milestone, issue milestone, auto cherry-pick, comment issue, GitHub Actions runner enable/delete, actions cache cleanup, feishu-message, webhook_utils.sh Use when changing label rules, milestone policies, cherry-pick targets, runner management, or bot message formats.

Cross-registry image mirroring and copy: skopeo sync, skopeo copy, docker.io, apecloud-registry.cn-zhangjiakou.cr.aliyuncs.com, infracreate-registry.cn-zhangjiakou.cr.aliyuncs.com, ECR, set_registry_and_repo.sh. Use when syncing images to Aliyun, copying images between registries, retagging images, or preparing offline image packages.

Container image build, check, push, and manifest management: release-image.yml, buildx, multi-arch amd64 arm64 manifest, helm_image_check.sh, manifests_image_check.sh, skopeo sync, image cache, push_images.sh. Use when image release fails, a new engine image is added, manifest image check fails, or amd64/arm64 platform support is missing.

Handle auxiliary CI/CD workflows in apecloud-cd: workflow trigger, database migration, OpenShift preflight, Red Hat certification. Use for migrate-database.yml, openshift-preflight.yml, or other workflows that do not fit into chart, image, e2e, or release domains.

Helm chart release workflow: helm package, chart-releaser cr, gh-pages index update, Jihulab chart upload, update_chart_values.sh, update_chart_annotations.sh, bump chart version. Use when packaging charts, publishing to helm-charts release, fixing chart index failures, or injecting release metadata into values.yaml and Chart.yaml.

ApeCloud / KubeBlocks Cloud multi-cluster deployment and cleanup: deploy-cloud.yml, cloud-cluster-clear.yml, IDC cleanup, terraform-init.yml, terraform-destroy.yml. Use when deploying to cloud environments, cleaning up IDC/IDC1/IDC2/IDC4 clusters, or debugging deployment failures.

Maintain the KubeBlocks all-version E2E workflow kubeblocks-e2e-test.yml. Engine matrix covers postgresql, redis, mongodb, clickhouse, elasticsearch, kafka, and 20+ engines. Use when adding/removing engine versions, updating send-message summary jobs, or checking consistency between test jobs, send-message jobs, and terraform-destroy-k8s needs.

KubeBlocks E2E testing infrastructure: kbcli-test.yml reusable workflow, kbcli-test-k8s.yml, cloud-e2e-*.yml, terraform-init, terraform-destroy, test-type, random-suffix. Use when adjusting kbcli-test parameters, adding E2E entry points, or changing cloud-e2e / terraform cluster lifecycle.

Execute real operations against the KubeBlocks Cloud API. Use this skill when users need to query, create, modify, or delete KubeBlocks Cloud resources.