kubeblocks-addon-rabbitmq

Provides legacy RabbitMQ provisioning compatibility shim for KubeBlocks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Legacy compatibility shim for RabbitMQ provisioning on KubeBlocks. The primary create-time entry remains kubeblocks-engine-rabbitmq, but this skill preserves older workflows and references for compatibility.

Core Features & Use Cases

  • Legacy compatibility shim for RabbitMQ provisioning on KubeBlocks
  • Keeps preserved workflow references for older clients
  • Documents the prerequisites and known limitations

Quick Start

Use this skill only to support legacy RabbitMQ provisioning when the main engine path is not available.

Frequently Asked Questions about kubeblocks-addon-rabbitmq

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

FAQPage Schema
What is the kubeblocks-addon-rabbitmq legacy compatibility shim used for?

The legacy compatibility shim preserves older RabbitMQ provisioning workflows on KubeBlocks for create-time deployments when older references rely on it and the primary engine path kubeblocks-engine-rabbitmq is unavailable.

Should I use kubeblocks-addon-rabbitmq or the primary engine for RabbitMQ provisioning on Kubernetes?

You should use the primary engine path kubeblocks-engine-rabbitmq for RabbitMQ provisioning. The kubeblocks-addon-rabbitmq shim is only for legacy compatibility when the main engine path is unavailable.

How do I handle legacy RabbitMQ provisioning references on KubeBlocks during create-time deployments?

Apply the kubeblocks-addon-rabbitmq shim to support legacy RabbitMQ provisioning references on KubeBlocks. It preserves the older workflow while delegating to the primary engine where possible and providing migration guidance.

Does KubeBlocks RabbitMQ provisioning support older workflow references when the main engine path is unavailable?

Yes, KubeBlocks supports older workflow references through the kubeblocks-addon-rabbitmq legacy compatibility shim. It ensures provisioning continuity during create-time deployments when the primary engine is unavailable.

What are the known limitations of using the legacy RabbitMQ compatibility shim on KubeBlocks?

The legacy RabbitMQ compatibility shim should not be used as the default runtime route for KubeBlocks provisioning. It is a temporary compatibility layer with documented limitations and clear guidance to migrate to the primary entry.