Expected: setting redis.auth.password as a chart value stores the password as a secret for use by other services in the same way that postgresql.auth.password is handled.
Behavior: When using an external Redis service, setting redis.auth.password as a chart value does not store the password for use by the other services. Currently, the value is only used to set the password for a Redis instance created by the chart. The only way to use an external Redis service is to set the password in an existingSecret outside of the chart.
This results in the error:
secret "mastodon-redis" not found: CreateContainerConfigError
Note that postgresql.auth.password gets stored in the mastodon.fullname secret name and the Redis secret is referenced from .Release.Name-redis secret name.
2023-07-19 edit: I have a pull request to fix this that I will submit tomorrow.
Expected: setting
redis.auth.passwordas a chart value stores the password as a secret for use by other services in the same way thatpostgresql.auth.passwordis handled.Behavior: When using an external Redis service, setting
redis.auth.passwordas a chart value does not store the password for use by the other services. Currently, the value is only used to set the password for a Redis instance created by the chart. The only way to use an external Redis service is to set the password in an existingSecret outside of the chart.This results in the error:
Note that
postgresql.auth.passwordgets stored in themastodon.fullnamesecret name and the Redis secret is referenced from.Release.Name-redissecret name.2023-07-19 edit: I have a pull request to fix this that I will submit tomorrow.