As per
The default ApplicationRegistration for RabbitMQCluster object scale-down strategy is based on changing CRD .spec.replica to 0.
Unfortunatelly isn't the case ... The Operator doesn't support scale-down at all
You can also see the Operator source Code here and it explains why it isn't supported
https://github.com/rabbitmq/cluster-operator/blob/e8384885e409d471a389d61cb09a11b3a64eacd8/controllers/reconcile_scale_down.go#L15
Unfortunately, the strategy for RabbitMQ is a little funky.
- Label
RabbitMQCluster object with the label
rabbitmq.com/pauseReconciliation: true
- Scale down RabbitMQCluster now unmanaged StatefulSet ( but still retains
ownerReferences
As per
stork/pkg/appregistration/appregistration.go
Line 242 in 77b30eb
The default ApplicationRegistration for RabbitMQCluster object scale-down strategy is based on changing CRD
.spec.replicato0.Unfortunatelly isn't the case ... The Operator doesn't support scale-down at all
You can also see the Operator source Code here and it explains why it isn't supported
https://github.com/rabbitmq/cluster-operator/blob/e8384885e409d471a389d61cb09a11b3a64eacd8/controllers/reconcile_scale_down.go#L15
Unfortunately, the strategy for RabbitMQ is a little funky.
RabbitMQClusterobject with the labelrabbitmq.com/pauseReconciliation: trueownerReferences