rabbitmq.conf not respected during container init

[dillonbailey]

Describe the bug

When deploying rabbitmq:4.1-management to an AKS cluster, the default_user and default_pass are not respected.

The below works in a local docker environment, but deploying the same to AKS results in the system continuing to use guest:guest

# /etc/rabbit/rabbitmq.conf
# this is a comment
default_user = '40696e180b610ed9'
default_pass = 'efd3!53a9@_2#a08'

auth_mechanisms.1 = PLAIN
auth_mechanisms.2 = AMQPLAIN
# note: the ANONYMOUS mechanism is not listed

# Value none has a special meaning that no user is configured for anonymous logins.
anonymous_login_user = none

# Dockerfile

FROM rabbitmq:4.1-management
ENV USER=rabbitmq
ENV GROUPNAME=$USER

COPY --chown=$USER:$GROUPNAME /etc/rabbitmq/rabbitmq.conf /etc/rabbitmq/rabbitmq.conf

Reproduction steps

1. Deploy the above to an AKS cluster
2. Attempt to login to the UI or connect to the cluster with the default creds from rabbitmq.conf
3. Unable to login
   ...

Expected behavior

Expected to be able to login with the default user/pass from rabbitmq.conf

Additional context

The rabbitmq deployment to AKS is a "StatefulSet" so it's not clear if this is causing some unexpected behaviour.

[mkuratczyk]

You have asked to "Deploy the above to an AKS cluster" but there's no YAML to deploy above...

Anyway, it sounds like it's some custom deployment template. The recommended way is to use the Operator:
https://www.rabbitmq.com/kubernetes/operator/using-operator

By default the Operator will set up random credentials. If you don't like it, you have a few options:
rabbitmq/cluster-operator#1875

Finally, you can use a Helm chart - another commonly used and well tested option.

If you indeed created a custom YAML to deploy RabbitMQ, please don't expect us to debug it.

Finally, this repo is for our website, so I'm closing the issue. If you are NOT using a custom deployment, please open the issue in the appropriate repo (cluster-operator or the helm chart repo).

[dillonbailey]

@mkuratczyk - thank you - that is really helpful and apologies for any headaches caused.

[michaelklishin]

@dillonbailey if you DIY RabbitMQ on Kubernetes, debugging your deployment and producing evidence are on you, you already get free software from our team and to my knowledge, you are not a contributor.

There is a dedicated doc section on troubleshooting authentication.

If you have a legitimate reason to ask a question in the future, please use GitHub Discussions in this repo, they have been enabled for years. Do not file issues, in particular in the website repository.

[dillonbailey]

@michaelklishin - thanks for the link to the DIY on Kubernetes, not something that surfaced after about 8 hours of research.

Appreciate that we are getting "free software", but to be honest, I opened the issue looking for guidance and hoping that if others were experiencing the same issue, that the community would be able to contribute and help to reduce effort required by maintainers or contributors. That's kind of the whole idea of free software. But we all have bad days. Sorry if this was a bother.

[michaelklishin]

That's what Discussions are for. Our team has expectations from those who expect free support, too.