You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allowing the redis.configmap parameter (or a new parameter) to replace a value in the redis configuration file instead of appending to the end of the file will make the bitnami/redis-cluster chart more flexible and allow using the default config map and only changing specific values instead of having to define an entire config map using redis.defaultConfigOverride.
What is the feature you are proposing to solve the problem?
Create a redis.configMapOverride parameter that will override existing entries in the default config map.
What alternatives have you considered?
Defining our own config map with redis.defaultConfigOverride, but part of the benefit of using this helm chart is having some defaults set already.
Modifying redis.args to set the relevant config map variables as part of the command line args, but then we drift away from any future changes made to the helm chart related to default args.
Modifying the template to add explicit parameters for each config map variable we want to customize, but this can become very cumbersome and verbose to account for all options.
The text was updated successfully, but these errors were encountered:
For some specific examples, when attempting to set redis RDB policy, both of the solutions below append the value 43200 1 to the existing config value instead of overwriting it. So as far as I can tell, there isn't a good way to overwrite the policy.
Name and Version
bitnami/redis-cluster 11.2.1
What is the problem this feature will solve?
Allowing the
redis.configmap
parameter (or a new parameter) to replace a value in the redis configuration file instead of appending to the end of the file will make the bitnami/redis-cluster chart more flexible and allow using the default config map and only changing specific values instead of having to define an entire config map usingredis.defaultConfigOverride
.What is the feature you are proposing to solve the problem?
Create a
redis.configMapOverride
parameter that will override existing entries in the default config map.What alternatives have you considered?
redis.defaultConfigOverride
, but part of the benefit of using this helm chart is having some defaults set already.redis.args
to set the relevant config map variables as part of the command line args, but then we drift away from any future changes made to the helm chart related to default args.The text was updated successfully, but these errors were encountered: