Clarification on “Day Two” Operations Managed by RabbitMQ Cluster Operator

[phil-fileread]

Hi team, first off thanks for all of the hard work done in this project.

The docs mention that the RabbitMQ Cluster Kubernetes Operator supports “day two” (continuous) operations:

The RabbitMQ Cluster Kubernetes Operator provides a consistent and easy way to deploy RabbitMQ clusters to Kubernetes and run them, including ‘day two’ (continuous) operations. RabbitMQ clusters deployed using the Operator can be used by applications running on Kubernetes or outside of Kubernetes.

I’m trying to get a clearer picture of which “day two” operations are actually handled by the operator.

So far, I understand that things like:
• pause-reconciliation
• Prometheus monitoring configuration (via annotations and service discovery)

…would fall under this umbrella. But I’m wondering:
• Are there other built-in or less-documented day two operations the Operator manages?
• Is there a complete list of day two features supported?

Thanks!

[mkuratczyk]

There's not that much but we may introduce more in the future. I'd add these to the list:

• queues are rebalanced after a cluster restart
• there's a preStop hook which prevents a node shutdown if there are components/queues/streams that'd lose quorum