kubeblocks-addon-kafka

Name: kubeblocks-addon-kafka
Availability: InStock
Author: ApeCloud

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

3|Updated Mar 12, 2026

Search Tags:#compatibility #engineering #kafka #legacy #addon #kubeblocks

Ready to run

npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-addon-kafka

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kubeblocks-addon-kafka
Source: https://github.com/apecloud/kubeblocks-skills/tree/main/skills/kubeblocks-addon-kafka
Command: npx skills add https://github.com/apecloud/kubeblocks-skills --skill kubeblocks-addon-kafka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Legacy Kafka provisioning requires maintaining old references; this shim preserves compatibility while guiding to the main entry.

Core Features & Use Cases

Provides a compatibility pathway for older Kafka addon references.
Delegates actual provisioning to kubeblocks-engine-kafka while preserving workflows.
Useful during migrations when upgrading to the primary engine without breaking existing scripts.

Quick Start

Invoke kubeblocks-addon-kafka to preserve compatibility while routing provisioning to kubeblocks-engine-kafka.

Frequently Asked Questions about kubeblocks-addon-kafka

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

FAQPage Schema

How do I maintain legacy Kafka provisioning references without breaking existing scripts during a KubeBlocks migration?▼

To maintain legacy Kafka provisioning references without breaking scripts, use a compatibility shim that routes old addon requests to KubeBlocks while delegating actual provisioning to the primary engine. This preserves existing workflows during migration.

What is the difference between kubeblocks-addon-kafka and kubeblocks-engine-kafka for Kafka deployments?▼

Kubeblocks-addon-kafka is a legacy compatibility shim that routes old provisioning references, while kubeblocks-engine-kafka is the primary path for new Kafka deployments. The addon defers actual provisioning to the canonical engine entry.

Do I need to update my existing Kafka addon references to migrate to the KubeBlocks engine?▼

No, you do not need to update existing Kafka addon references immediately. The compatibility shim intercepts legacy provisioning requests and routes them to the KubeBlocks engine, allowing gradual migration without breaking scripts.

When should I use the legacy Kafka provisioning shim instead of the primary engine path?▼

Use the legacy Kafka provisioning shim when your existing scripts and operators reference the old addon entry point. For all new Kafka deployments, use the kubeblocks-engine-kafka path directly as the canonical provisioning method.

Can I run kubeblocks-addon-kafka as a standalone Kafka provisioning tool?▼

No, kubeblocks-addon-kafka is not a standalone provisioning tool. It is a compatibility shim that documents the legacy workflow and defers all actual Kafka provisioning operations to the kubeblocks-engine-kafka canonical entry.

Why does my legacy Kafka addon reference still work after upgrading KubeBlocks?▼

Your legacy Kafka addon reference works because the compatibility shim intercepts old provisioning requests and routes them to the new KubeBlocks engine. This ensures existing references remain functional without requiring code changes.