Skip to content

RabbitMQ Kubernets Operator doesn't allow scale down operations #1881

@drgogeta86

Description

@drgogeta86

As per

Path: "spec.replicas",

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.

  1. Label RabbitMQCluster object with the label
    rabbitmq.com/pauseReconciliation: true
  2. Scale down RabbitMQCluster now unmanaged StatefulSet ( but still retains ownerReferences

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions