Yeah I came across this the other day. It’s a bug with how some helm charts regenerate the secret containing the password on an upgrade - see this thread for more details.
So basically every time you do a
helm upgrade with the stable chart, you’ll need to have made a note of the existing value in the
sentry-redis secret before the upgrade so you can edit the secret to put it back afterwards.
Obviously if you aren’t aware of this, and now need to find a way to get the original password, you can follow these steps (from a comment in the same thread):
- Exec into the running Redis container
kubectl exec -ti sentry-redis-XXX bash
- Find the old password
grep requirepass /opt/bitnami/redis/etc/redis.conf
- Update your secret to use that password (restart services as needed)
It’s worth noting that this issue is now fixed upstream in the redis chart, but the stable sentry chart is not using it yet