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
Hi,
since redis changed their licence type we are thinking about a move to the valkey fork. The argocd community is also discussing it, see: argoproj/argo-cd#17970
Currently the valkey image seems to be 100% compatible - the redis-ha chart still works good after replacing the redis image with valkey (tested with 8.0.1). But this can change in the future.
So we see the option to move to a different chart - I found only 2 options so far:
(bitnami - not our preferred option) https://github.com/bitnami/charts/tree/main/bitnami/valkey
(groundhog2k - small and new, but unclear adoption) https://github.com/groundhog2k/helm-charts/tree/master/charts/valkey
So my question is now: Do you think you will support the valkey images in the future? (especially if they will be incompatible)
Or is this totally out of your scope and you will focus on redis only.
Thanks in advance for clarification,
Sven
The text was updated successfully, but these errors were encountered:
Hi,
since redis changed their licence type we are thinking about a move to the valkey fork. The argocd community is also discussing it, see: argoproj/argo-cd#17970
Currently the valkey image seems to be 100% compatible - the redis-ha chart still works good after replacing the redis image with valkey (tested with 8.0.1). But this can change in the future.
So we see the option to move to a different chart - I found only 2 options so far:
(bitnami - not our preferred option) https://github.com/bitnami/charts/tree/main/bitnami/valkey
(groundhog2k - small and new, but unclear adoption) https://github.com/groundhog2k/helm-charts/tree/master/charts/valkey
So my question is now: Do you think you will support the valkey images in the future? (especially if they will be incompatible)
Or is this totally out of your scope and you will focus on redis only.
Thanks in advance for clarification,
Sven
The text was updated successfully, but these errors were encountered: