KubeBlocks for
RabbitMQ
RabbitMQ is the most widely deployed open-source message broker. It supports multiple messaging protocols including AMQP, MQTT, and STOMP, enabling reliable asynchronous communication, task queues, and pub/sub patterns across distributed systems.
Supported versions
Available on
AWS
Azure
GCP
OCI
OpenShiftDatabases
MySQL
PostgreSQL
Oracle
SQL Server
Redis
ClickHouseVector & AI
Milvus
ElasticsearchMessage queues
KafkaOthers
etcdExtend database engines like plug-ins
KubeBlocks provides unified database operations through its addon-based architecture. With KubeBlocks Enterprise, access over 15 seamless integrations to scale your database services.
One control plane, consistent operations across all engines — powered by the addon mechanism.
Run RabbitMQ with real user, monitoring, and parameter workflows
Operate RabbitMQ on Kubernetes with console-backed evidence for lifecycle, user management, observability, and configuration workflows, while keeping current console limits such as web-console enablement, stop/start, and backup-route gaps visible to buyers and operators.
Lifecycle
Deploy RabbitMQ clusters and monitor rolling service changes
Create RabbitMQ with the tested clustered topology, keep runtime state visible from the overview, and follow restart and cleanup workflows from the same operational surface.
- Launch RabbitMQ with the tested 4.2.1 clustered deployment, storage profile, and baseline compute footprint.
- Track rolling restart progress with live task banners and topology health on the overview page.
- Use the cluster workspace for deletion and cleanup after test validation is complete.

The overview keeps RabbitMQ topology and lifecycle controls visible as soon as the cluster reaches Running.

Rolling restart progress stays visible in context so teams can follow broker recovery from the same page.
Scale
Review replica scaling from the RabbitMQ cluster workspace
RabbitMQ exposes Replica Scaling from the overview so teams know where node-count changes are meant to happen, and the captured console state records the current UI limit seen during validation.
- Open Replica Scaling directly from the running cluster rather than editing infrastructure objects by hand.
- See the intended replica target control in the same workflow used for day-2 operations.
- The tested console kept the target replica count pinned at `3`, so no scaling task was created in this run.

The real scaling dialog shows where RabbitMQ capacity changes are initiated and documents the current replica-selection blocker.
Parameter
Review RabbitMQ engine settings before controlled reconfiguration
Use the Parameters workspace to inspect `rabbitmq.conf` values and prepare configuration updates with a clear view of which settings require a restart.
- Inspect RabbitMQ parameter values from a dedicated configuration view.
- Prepare broker behavior changes without leaving the cluster console.
- See reboot-required markers before planning configuration rollout windows.

Parameter management helps teams review RabbitMQ settings and understand restart requirements before applying changes.
Accessibility
Check where RabbitMQ access policy would be managed
RabbitMQ exposes Access Rules entry points for SSL and IP Whitelist review, while the tested engine state makes it explicit that this feature is not currently available for execution.
- Open the Access Rules route from the cluster workspace to review the available policy surface.
- See SSL and IP Whitelist tabs in the same place application connectivity would be governed.
- Use the captured unsupported state to set accurate expectations before onboarding workloads.

The Access Rules page makes the current RabbitMQ access-policy limitation explicit instead of hiding it behind missing navigation.
Data Management
Create RabbitMQ users and see the web console handoff path
Manage RabbitMQ credentials from the console and capture the real handoff into Data Management, including the tested blocker that prevented enabling the management UI for queue and message workflows.
- Create RabbitMQ accounts from the Credentials page for application and team access.
- Review where Data Management would enable the management UI for queue administration and message testing.
- The tested enablement dialog returned empty `Network Mode` and `Service Type` selectors, so queue creation and publish-consume flows could not proceed.

Credentials management gives teams a real user workflow today for RabbitMQ application access.

The captured enablement dialog shows the exact handoff point into the RabbitMQ management UI and the current blocker seen during validation.
Observability
Monitor RabbitMQ cluster health and inspect runtime behavior
Track cluster health from metrics dashboards and move into runtime logs when teams need to understand listener startup, management plugin activity, or broker state transitions.
- Use Cluster Monitor views to watch RabbitMQ health after metrics panels hydrate.
- Inspect real runtime log output for listeners, plugins, and broker startup events.
- Keep monitoring and troubleshooting workflows close to the same cluster detail surface.

Metrics dashboards give teams a live RabbitMQ health view without leaving the console.

Runtime logs make it easier to verify RabbitMQ listener and management-plugin behavior during troubleshooting.
Audit
Keep RabbitMQ operational history visible through task records
Use task history to confirm what ran, what succeeded, and which day-2 operations produced real state changes during cluster management.
- Review completed RabbitMQ restart activity from a dedicated task timeline.
- See when operational actions succeeded before handing the cluster back to users.
- Use the task page as lightweight audit evidence for operational review.

Task history provides a compact audit trail for RabbitMQ operations that completed in the console.
Ready to build your own DBaaS on Kubernetes?
Talk to our team and see how KubeBlocks Enterprise can help you consolidate databases, strengthen security, and reduce operational costs.

