Hi Ralph,
This is a known limitation with the Topology Operator. The Topology Operator reads the k8s default user secret set in RabbitmqCluster status `status.binding` to authenticate with RabbitmqCluster. If the RabbitmqCluster is deployed with pre defined default user creds like your example, the provided creds will overwrite the default user credentials that's auto generated and stored in the default user k8s secret and therefore cause Messaging Topology Operator not be able to access the RabbitmqCluster. You can check the default user secret context to verify. The secret object name follows the pattern of "RabbitmqClusterName-default-user" and it's created in the same namespace.
To get around this issue, either you can stop setting the user creds (like what you did), or you can manually update the content of the default user kubernetes secret to the actual user credentials set by you in spec.rabbitmq.additionalConfig.
Thanks,
Chunyi