You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Optionally enable all feature flags automatically (#1892)
* Add `autoEnableAllFeatureFlags` property
Default to false. When set to true, all feature flags are automatically
enabled immediately after each upgrade (we don't check
if there are new feature flags - in most cases, this command
is a no-op). Note that when upgrade to RabbitMQ 4.2, this means
Khepri is gets enabled just after the upgrade
(again, if the property is set to true).
Co-authored-by: Aitor Pérez Cedres <[email protected]>
Copy file name to clipboardExpand all lines: docs/api/rabbitmq.com.ref.asciidoc
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -382,6 +382,8 @@ Must be provided together with ImagePullSecrets in order to use an image in a pr
382
382
Set to true to prevent the operator rebalancing queue leaders after a cluster update.
383
383
Has no effect if the cluster only consists of one node.
384
384
For more information, see https://www.rabbitmq.com/rabbitmq-queues.8.html#rebalance
385
+
| *`autoEnableAllFeatureFlags`* __boolean__ | Set to true to automatically enable all feature flags after each upgrade
386
+
For more information, see https://www.rabbitmq.com/docs/feature-flags
385
387
| *`terminationGracePeriodSeconds`* __integer__ | TerminationGracePeriodSeconds is the timeout that each rabbitmqcluster pod will have to terminate gracefully.
386
388
It defaults to 604800 seconds ( a week long) to ensure that the container preStop lifecycle hook can finish running.
387
389
For more information, see: https://github.com/rabbitmq/cluster-operator/blob/main/docs/design/20200520-graceful-pod-termination.md
0 commit comments