Enable all feature flags when deploying a new cluster #414
Assignees
Milestone
Comments
ansd
added a commit
that referenced
this issue
Oct 29, 2020
ansd
added a commit
that referenced
this issue
Oct 30, 2020
ansd
added a commit
that referenced
this issue
Oct 30, 2020
ansd
added a commit
that referenced
this issue
Nov 3, 2020
* Enable all feature flags for new clusters Closes #414 * Rename post deploy to CLI because the RabbitMQ CLI commands get executed at the end of the reconcile loop which does not necessarily mean that a deployment just finished. This commit also fixes a bug where the rabbitmq-plugins command was run on every successful reconile loop.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some feature flags are disabled by default because RabbitMQ itself cannot tell whether it's starting a fresh node or not at the time it needs to decide the state of a feature flag. To be on the safe side - those flags are disabled. The operator however, can distinguish between a fresh cluster deployment and update/upgrade and should therefore enable all feature flags when deploying a new cluster so that all features are available by default. At this time, these disabled-by-default feature flags are
drop_unroutable_metricandempty_basic_get_metricbut ideally, we should make the implementation generic so that we always enable all feature flags when deploying a new cluster.The text was updated successfully, but these errors were encountered: