v2.13.0

⚠️ Upgrading the cluster-operator to this version will update RabbitMQ clusters (i.e. will cause rolling update of the underlying StatefulSets).
If you want to control when a RabbitMQ cluster gets updated, make sure to pause reconciliation before upgrading the cluster-operator.
After upgrading the cluster-operator, resume reconciliation whenever it's safe to update the RabbitMQ cluster.
See Pause reconciliation for a RabbitMQ cluster.

What's Changed

• Use rabbitmq:4.1.0-management as the default image by @mkuratczyk in #1867
• Reduce init container memory from 500Mi to 64Mi and CPU from 100m to 20m by @mkuratczyk in #1863
• Add support for custom Service labels via spec.service.labels by @EladAviczer in #1859
• PrometheusRule for rabbitmq alarm states by @awoimbee in #1823
• Improve cluster deletion by @mkuratczyk in #1864
• Add promtool for alert rule validation by @mkuratczyk in #1824
• configure rules to merge rabbitmq_identity_info by @mmueller-rs in #1856
• Bump (almost) all deps by @mkuratczyk in #1866
• Modernize the codebase by @mkuratczyk in #1868
• adding back replaces field on operatorhub publication by @DanielePalaia in #1815

New Contributors

• @awoimbee made their first contribution in #1823
• @mmueller-rs made their first contribution in #1856
• @EladAviczer made their first contribution in #1859

Full Changelog: v2.12.1...v2.13.0