Skip to content

Conversation

@ansd
Copy link
Member

@ansd ansd commented Aug 15, 2022

Since we dropped support for RabbitMQ 3.8 in #1110, we can now simplify the cluster-operator:

  1. Remove deprecated cluster_formation.randomized_startup_delay_range configurations such that warning [warn] <0.130.0> cluster_formation.randomized_startup_delay_range.min and cluster_formation.randomized_startup_delay_range.max are deprecated won't be output anymore in RabbitMQ logs. See Remove randomized startup delays rabbitmq-server#3075.
  2. Use rabbitmqctl enable_feature_flag all command introduced by @mkuratczyk and @michaelklishin in rabbitmq/rabbitmq-server@ce65586.

ansd added 3 commits August 15, 2022 08:24
Since we bumped the minimum supported RabbitMQ version to v3.9.0 in
#1110, we can use the
CLI command `rabbitmqctl enable_feature_flag all` introduced in
rabbitmq/rabbitmq-server@ce65586.
Since we bumped the minimum supported RabbitMQ version to v3.9.0 in
#1110, we can delete
the deprecated `cluster_formation.randomized_startup_delay_range`
configurations.

See rabbitmq/rabbitmq-server#3075.

Prior to this commit, the RabbitMQ logs contained the following warning:
```
2022-08-15 08:18:03.870480+00:00 [warn] <0.130.0> cluster_formation.randomized_startup_delay_range.min and cluster_formation.randomized_startup_delay_range.max are deprecated
```
Follow up of #1110:
The new minimum supported version is 3.9.0.
Therefore, we should test against that version to make sure the
cluster-operator is compatible with the minimum supported version.
Copy link
Contributor

@coro coro left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love it. Let's make sure to be explicit in our release notes for this cluster operator version then since we're now explicitly relying on behaviour in 3.9 rather than implicitly dropping support for 3.8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants