Release Notes¶
Welkin RabbitMQ¶
- v4.2.5-ck8s1 - 2026-04-02
- v4.1.4-ck8s1 - 2025-10-16
- v4.0.6-ck8s3 - 2025-05-20
- v4.0.6-ck8s2 - 2025-04-25
- v4.0.6-ck8s1 - 2025-02-28
- v3.13.7-ck8s1 - 2024-12-09
- v3.12.6-ck8s1 - 2024-01-17
- v3.11.18-ck8s1 - 2023-07-03
- v3.10.7-ck8s1 - 2022-09-21
- v1.11.1-ck8s2 - 2022-06-08
- v1.11.1-ck8s1 - 2022-03-11
- v1.7.0-ck8s1 - 2021-12-23
Note
These are only the user-facing changes.
v4.2.5-ck8s1¶
Released 2026-04-02
Application Developer Notice(s)
- RabbitMQ has been upgraded to v4.2.
- With RabbitMQ v4.2 the default value for AMQP 1.0 durable field has changed to false to comply with the specification. Applications must set the durable field to true to mark messages as durable. This is recommended by upstream and all their AMQP 1.0 libraries send messages as durable by default.
- With RabbitMQ v4.2 if an AMQP 0.9.1 Direct Reply-To responder (RPC server) publishes messages with the
mandatoryfield set thenamq.rabbitmq.reply-to.*will be treated as a queue. RabbitMQ does not check at routing time whether the requester is still consuming the reply. The message will be considered routed, so nobasic.returnis sent. - During the upgrade, servers in the Clusters will restart one by one, causing disruptions as applications must reconnect to another server. If durable classic queues are used, expect unavailability while the server hosting the queue is upgraded, or migrate to distributed queues such as quorum queues. During the upgrade the metadata store will be migrated to Khepri instead of Mnesia, this should not impact the usability of RabbitMQ, unless it fails in which case the servers will restart to re-enable Mnesia.
- See the upstream release notes for more details.
Improvements(s)¶
- RabbitMQ has been upgraded to v4.2.
- Metadata store will be migrated to Khepri, which will bring consistency and stability benefits in events of high latency or network issues.
v4.1.4-ck8s1¶
Released 2025-10-16
Application Developer Notice(s)
- RabbitMQ has been upgraded to version 4.1. Read through the breaking changes of this version.
- Most notably users of amqplib (a popular library for node.js) must upgrade to a compatible version.
- Network policies for external traffic now properly adapt based on exposed ports.
- Allow applications to use the HTTP(S) management API from application developer namespaces.
Improvement(s)¶
- RabbitMQ has been upgraded to v4.1.
- A
PodDisruptionBudgetis now configured for the RabbitMQ Cluster to ensure high availability during voluntary disruptions. - The "RabbitMQ-Overview" Grafana dashboard has been updated.
v4.0.6-ck8s3¶
Released 2025-05-20
Application Developer Notice(s)
- Allow applications to use the HTTP(S) management API from application developer namespaces.
- Network policies for external traffic now properly adapt based on exposed ports.
Improvement(s)¶
- deploy: Add Network Policy enabled flag, enabled by default
- deploy: Allow internal management from application developer namespaces
Other(s)¶
- bug - deploy: Rework internal and external Network Policy rules
- bug - scripts: Handle CNAME records for object storage hosts
v4.0.6-ck8s2¶
Released 2025-04-25
Other(s)¶
- Correct script to update Cluster DNS for Network Policies, no Application Developer facing change.
v4.0.6-ck8s1¶
Released 2025-02-28
Application Developer Notice(s)
- Added Network Policies:
- For new clusters, these will deny access to the RabbitMQ cluster by default. To gain access to the RabbitMQ clusters, add this label to your pods:
elastisys.io/rabbitmq-<cluster_name>-access: allow - For existing clusters, these will not deny access to the RabbitMQ cluster by default. Once your pods have been labeled with
elastisys.io/rabbitmq-<cluster_name>-access: allow, enforcement can be enabled by sending a Service Request to your Platform Administrator.
- For new clusters, these will deny access to the RabbitMQ cluster by default. To gain access to the RabbitMQ clusters, add this label to your pods:
- AMQP 1.0 is now a core protocol, and is always enabled.
Classic queue mirroring is now removed.
Feature(s)¶
- Network Policies are added to the Cluster deployments which will deny access by default.
Improvement(s)¶
- RabbitMQ is upgraded v4.0, which is a new major release.
v3.13.7-ck8s1¶
Released 2024-12-09
Improvement(s)¶
- Updated Cluster operator to
2.9.0, updated server to3.13.7and monitoring to2.9.0. - Updated the backup process to use
rabbitmqctlfor improved reliability and compatibility. - Added a
LICENSEfile to the repository to provide clarity on usage and distribution.
v3.12.6-ck8s1¶
Released 2024-01-17
Updated¶
- Updated server to
3.12.6 - Update release process and use new changelog generator
v3.11.18-ck8s1¶
Released 2023-07-03
Updated¶
- Updated Cluster operator to
v2.3.0, updated server to3.11.18 - Include updated Overview dashboard
v3.10.7-ck8s2¶
Released 2022-11-28
Fixed¶
- Corrected the Queue Details Grafana dashboard and improved alerting
v3.10.7-ck8s1¶
Released 2022-09-21
Note
From this release the version tracks the RabbitMQ server version rather than the RabbitMQ cluster operator version.
Updated¶
- Upgraded RabbitMQ server version to
3.10.7
This is a two minor version jump that introduces new upstream features while remaining compatible with current clients. The most exciting features includes the new Stream queue type tuned for bulk messaging, and much improved efficiency for Quorum and Classic queue types. See the upstream changelog for more detailed information.
Added¶
- Added support for external access
Using either a LoadBalancer or NodePort Service, additionally with a self-signed chain of trust to enable TLS and host verification.
Changed¶
- Improved observability
Improved the alerting and replaced the per queue metrics source and dashboard, removing the need for an external exporter.
v1.11.1-ck8s2¶
Released 2022-06-08
Changed¶
- Reworked monitoring
Added additional metrics collection and a new dashboard to show metrics per queue, and fixed those added by the previous release. - Tuned performance
Configured and tuned the performance according to RabbitMQ upstream production checklist. Including better constraints to improve scheduling for redundancy.
v1.11.1-ck8s1¶
Released 2022-03-11
Updated¶
- Upgraded RabbitMQ to version
3.8.21
Using Cluster operator version1.11.1providing bugfixes.
Added¶
- Added definitions-exporter
Taking daily backups of the RabbitMQ messaging topology and users for quick and easy reconfiguring in case of disaster.
Changed¶
- Reduced RabbitMQ privilege for security.
- Improved RabbitMQ observability through better monitoring.
v1.7.0-ck8s1¶
Released 2021-12-23
First stable release using RabbitMQ version 3.8.16!