Diese Seite ist nur auf Englisch verfügbar.
RabbitMQ version support
The RabbitMQ version BCI supports is up to the latest 4.1.x.
RabbitMQ versions included in different releases of the SOT Infrastructure Helm chart:
| Artifact | Version | Contained RabbitMQ Version |
|---|---|---|
nexeed-infra |
1.1.x |
3.11.x |
nexeed-infra |
1.2.x |
3.12.x |
nexeed-infra |
1.3.x |
3.13.x |
nexeed-infra |
2.0.x |
4.1.x |
|
Please be aware that it is not recommended to "skip" RabbitMQ minor versions. For example, if RabbitMQ 3.11.x is in use, it should be updated to 3.12.x before an update to 3.13.x is performed. |
Custom configuration
BCI does not support RabbitMQ in the configuration outside what BCI can provide.
Examples of such configurations include:
-
Custom port numbers
-
Cluster formation methods and plugins
-
and more…
RabbitMQ infrastructure
Depend on how many Kubernetes worker nodes a cluster has, the RabbitMQ has either 1 or 3 Pods.
This is controlled automatically by using the Kubernetes podAntiAffinity
feature, it will not deploy the RabbitMQ pods on the same node or zone depends
on your deployment target type to try to reach high availability.
Disclaimer With the SOT 2025.02.01 release, the RabbitMQ Classic Mirror Queues are now disabled by default. The SOT system will use Quorum Queues as default. If you would still like to use the Classical Queues (with Mirror Policy), you can do so by changing this parameter to "enabled" in your custom-values file.
rabbitmq:
rabbitMqClassicMirrorQueuesPolicy: enabled