Authentication failure due to RabbitMQ credential mismatch between secrets

Celery workers fail to authenticate with RabbitMQ because celery-broker-secret and rabbitmq-default-user secrets contain different credentials. This occurs when RabbitMQ regenerates credentials or Helm creates new secrets, causing drift between the two secret stores.

Compare credentials between secrets using kubectl get secret commands. If mismatched, patch celery-broker-secret to sync with rabbitmq-default-user credentials using kubectl patch, then restart worker deployment with kubectl rollout restart.