Mailu
feat(helm)!: Update chart redis ( 22.0.7 ➔ 23.2.3 )
This PR contains the following updates:
| Package | Update | Change |
|---|---|---|
| redis (source) | major | 22.0.7 -> 23.2.3 |
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
![renovate[bot] avatar](https://avatars.githubusercontent.com/in/2740?v=4 "Published by a pub.dev verified publisher"){kind=small}
With the things going on with bitnami, we should move this to bitnamilegacy, or change for another keyvalue store such as valkey or keydb
With the things going on with bitnami, we should move this to bitnamilegacy, or change for another keyvalue store such as valkey or keydb
The images are already migrated to bitnamilegacy, the charts are not, but I support the effort in migrating somewhere else and personally prefer valkey
I just looked into https://github.com/valkey-io/valkey-helm and it seems like a suitable replacement
I have been replacing redis with valkey on different occasions as well. It tends to fit in rather nicely, since valkey is a redis fork.
I am unsure if the data that is inside redis in this project needs to be migrated, or if it can be removed and will simply be repopulated as needed?
The data has to be migrated. Valkey is able to work with the stored data from redis so we just have to make sure that the same PVC is used but that should work