Name and Version
bitnami/rabbitmq --version 16.0.14
What steps will reproduce the bug?
From doc "The Bitnami RabbitMQ chart, when upgrading, reuses the secret previously rendered by the chart or the one specified in auth.existingSecret."
but in fact in help upgrade
for example i added
sectet is recreated
here is the proof
root@vps151432-xf5:~# kubectl get secret rabbitmq -n rabbitmq \
-o jsonpath='{.data.rabbitmq-password}' | base64 -d
echo
oacumK6B1LInvKjZ
root@vps151432-xf5:~#
root@vps151432-xf5:~#
root@vps151432-xf5:~# kubectl get secret rabbitmq -n rabbitmq \
-o jsonpath='{.data.rabbitmq-password}' | base64 -d
echo
2Wqp4XkRlpKObNNJ
Name and Version
bitnami/rabbitmq --version 16.0.14
What steps will reproduce the bug?
From doc "The Bitnami RabbitMQ chart, when upgrading, reuses the secret previously rendered by the chart or the one specified in auth.existingSecret."
but in fact in help upgrade
for example i added
sectet is recreated
here is the proof