v2.17.0
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.
Potential breaking changes
For Openshift users, the enhanced security context might cause downtime if the security context is not overridden, as documented in our updated example or our website docs.
Enhanced Security Context
The cluster operator now has a security context, and sets an enhanced security context for RabbitMQ clusters. For users on OpenShift and other cases where the security context is overridden, please make use of our updated example.
What's Changed
- Add dependabot groups. by @MirahImage in #1943
- Bump tools and deps by @Zerpet in #1938
- Use github packages for our container image by @Zerpet in #1939
- fix unnecessary memory-not-equal warnings by @chengjoey in #1954
- Make unit and integration tests run in parallel by @Zerpet in #1942
- Add security context by @MirahImage in #1961
- set endPort as default in the netpols examples by @3deep5me in #1963
- Change actions to run documented examples in parallel with matrix. by @MirahImage in #1967
- Allow overriding container security context. by @MirahImage in #1965
- Fix RabbitMQ log output with Vault configured by @ansd in #1971
New Contributors
- @chengjoey made their first contribution in #1954
- @3deep5me made their first contribution in #1963
Full Changelog: v2.16.1...v2.17.0
