Applications use RabbitMQ to pass messages between producers and consumers that do not have to run at the same pace. The historical rabbitmq-ha chart packaged several brokers with an older high-availability design intended to keep messaging available through failures. That chart is retired, and its queue-mirroring assumptions do not carry into RabbitMQ 4. A replacement must preserve the application’s delivery expectations and queued work, not merely produce the same number of ready broker pods.
Current guidance
This retirement label applies to the stable/rabbitmq-ha package, whose own README says it is no longer maintained. RabbitMQ remains a separate, current broker project. The old chart’s historical recommendation to switch publishers is not sufficient modern migration advice: distribution, broker version and queue semantics must all be reviewed.
RabbitMQ documentation states that classic queue mirroring was removed in 4.0 and directs replicated-queue users toward quorum queues or streams. Those alternatives have different behavior and workload constraints. Inventory queue types, policies, durability, publisher confirms, consumer acknowledgements and client retry behavior before selecting a new chart or the official Cluster Operator.
Preserve definitions and credentials, but recognize that a definitions export is not the queued messages. Rehearse a supported queue migration with bounded traffic, measure backlog drainage and validate redelivery behavior. Keep cluster identity and Erlang-cookie handling deliberate rather than copying resources between releases. Do not claim that three ready broker pods prove safe replication or that a Helm rollback reverses a queue-type conversion.
Historical upstream link check · 2026-10-09
The recorded upstream address responded successfully (HTTP 200) on 2026-10-09. GitHub confirms that helm/charts is archived: this is a historical chart distribution, not evidence that the application itself is retired. Link availability does not certify the historical installation instructions or current security support.
Website availability is separate from project, chart and image support. Use the current guidance and primary sources on this page to assess the distribution.
Historical Kubedex content
Original publication: 2018-09-16T11:50:37+00:00. Preserved for context. Commands, versions, prices and results below reflect the original research.
RabbitMQ is an open source message broker software that implements the Advanced Message Queuing Protocol (AMQP). With more than 35,000 production deployments of RabbitMQ world-wide at small startups and large enterprises, RabbitMQ is the most popular open source message broker.
RabbitMQ is lightweight and easy to deploy on premises and in the cloud. It supports multiple messaging protocols. RabbitMQ can be deployed in distributed and federated configurations to meet high-scale, high-availability requirements. RabbitMQ runs on many operating systems and cloud environments, and provides a wide range
of developer tools for most popular languages.
RabbitMQ Features
Asynchronous Messaging: Supports multiple messaging protocols, message queuing, delivery acknowledgement, flexible routing to queues, multiple exchange type.
Developer Experience: Deploy with BOSH, Chef, Docker and Puppet. Develop cross-language messaging with favorite programming languages such as: Java, .NET, PHP, Python, JavaScript, Ruby, Go, and many others.
Distributed Deployment: Deploy as clusters for high availability and throughput; federate across multiple availability zones and regions.
Enterprise & Cloud Ready: Pluggable authentication, authorization, supports TLS and LDAP. Lightweight and easy to deploy in public and private clouds.
Tools & Plugins: Diverse array of tools and plugins supporting continuous integration, operational metrics, and integration to other enterprise systems. Flexible plug-in approach for extending RabbitMQ functionality.
Management & Monitoring: HTTP-API, command line tool, and UI for managing and monitoring RabbitMQ.
RabbitMQ Commercial Distribution
Pivotal Software produces a commercial distribution called Pivotal RabbitMQ, as well as a version that deploys in Pivotal Cloud Foundry. These distributions include all of the features of the open source version, with RabbitMQ for Pivotal Cloud Foundry providing some additional management features. Support agreements are part of the commercial licensing.
The post RabbitMQ HA appeared first on kubedex.com.
Sources & further reading
Spotted something that needs another look?
Help improve this page →