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
Is your feature request related to a problem? Please describe.
The operator creates a default user for a RabbitMQ Cluster, with a random username/password. This is done through the configuration in /etc/rabbitmq/conf.d/default_user.conf as of #346.
The Secret containing the credentials of this user is presented in the Status field of the RabbitmqCluster CR:
The issue is, this user doesn't have to be an admin. A user can specify that the default user, for whatever reason, is not admin, by setting default_user_tags.administrator = false in their additionalConfig. Usually, the administrator tag is present:
$ k exec bunny-rabbitmq-server-0 rabbitmqctl list_users
Listing users ...
user tags
kYbsLQFdSA-Z4ZY6BBitcFdazPeLPowo [administrator]
However, creating a cluster with the following spec:
creates an 'admin' user that isn't actually an admin!
$ k exec foo-cluster-rabbitmq-server-0 rabbitmqctl list_users
Listing users ...
user tags
7PD4ho7fjS8EPAoHmn8aLL8pfb8HVK9h []
The status for this CR still reports the creds under 'Admin', however.
Describe the solution you'd like
Any default user configuration should still be displayed in the Status of the CR, but representing the user (and optionally its permissions / tags) as a default, rather than an admin. For a rough example:
Is your feature request related to a problem? Please describe.
The operator creates a default user for a RabbitMQ Cluster, with a random username/password. This is done through the configuration in
/etc/rabbitmq/conf.d/default_user.conf
as of #346.The Secret containing the credentials of this user is presented in the Status field of the RabbitmqCluster CR:
The issue is, this user doesn't have to be an admin. A user can specify that the default user, for whatever reason, is not admin, by setting
default_user_tags.administrator = false
in theiradditionalConfig
. Usually, the administrator tag is present:However, creating a cluster with the following spec:
creates an 'admin' user that isn't actually an admin!
The status for this CR still reports the creds under 'Admin', however.
Describe the solution you'd like
Any default user configuration should still be displayed in the Status of the CR, but representing the user (and optionally its permissions / tags) as a default, rather than an admin. For a rough example:
Note the secret name has been changed to have a
-default-user
suffix rather than-admin
.The text was updated successfully, but these errors were encountered: