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
Currently, when we use Access Control Lists (ACL) or update some configuration with Command-Line Interface (CLI), all changes are lost on pod update, and there is no persistence of the redis.conf file. This behavior is inconvenient as it requires manually recreating the configuration file after each update.
One possible solution is to use the /data directory as the default directory for this file. This approach would allow for the configuration file to persist across updates, ensuring that changes made with ACL or CLI are retained.
Currently, when we use Access Control Lists (ACL) or update some configuration with Command-Line Interface (CLI), all changes are lost on pod update, and there is no persistence of the redis.conf file. This behavior is inconvenient as it requires manually recreating the configuration file after each update.
One possible solution is to use the /data directory as the default directory for this file. This approach would allow for the configuration file to persist across updates, ensuring that changes made with ACL or CLI are retained.
To implement this solution, we suggest modifying the secret-utils.yaml file located at https://github.com/Enapter/charts/blob/master/keydb/templates/secret-utils.yaml#L21. Specifically, we recommend updating the file to specify the /data directory as the default directory.
What do you think about it?