Question (redis-ha): is valkey support planned for the future?

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

I don't personally have objection to a native OSS alternative to prevent licensing issues for consumers of the chart.

I haven't tested this with the chart out of the box.

I think with ArgoCD being the biggest downstream consumer of this that (that I'm aware of), I would happily follow their lead as a community.

The biggest test that needs doing is HA and adjustments to facilitate in something like Valkey.

https://github.com/hyperspike/valkey-operator

i think someone is working on operator. It is a different solution tho.

This is a really interesting feature.

@pierluigilenoci

@pierluigilenoci I've come back to this again as well, I think this would be better as its own chart.

Eventually, Valkey / Redis will branch off in different directions on how to interact with their clients and supporting 2 different charts would be simpler in the long term.

Example being Elasticsearch / Opensearch and how they drifted completely apart and Opensearch ended up breaking the larger managed community chart because of that drift.

Hey.
The second biggest downstream user of your chart is oauth2-Proxy, (or so I think), after ArgoCD.
But in both cases, doesn't using Redis as part of their product or distribution medium go against both of these project's OSS License ?

@DandyDeveloper

Hi @DandyDeveloper is the chart for valkey still under develop ?

@erolclk1

@erolclk1 Right now, it's purely a time issue for me. I don't have time to spend on this lately with real work and personal life.

I'm more than happy for someone to extract what they can and make a Valkey chart, I may have a branch somewhere that started this. I just never got time to do it.

just as an info: we are currently using the valkey 9.0 image with redis-ha chart version: 4.34.11 - works fine. So far the valkey image seems to be 100% compatible.

I've been using the chart with Valkey for ages, more or less since the fork happened. The only thing I've found I need to change is to put this in the values file:

sentinel:
  customCommand: [valkey-server]
  customArgs: [/data/conf/sentinel.conf, --sentinel]

I added those settings in 2024 with #277.

Valkey also now has it's own helmchart: https://github.com/valkey-io/valkey-helm

Navigation Menu

Repository navigation

Question (redis-ha): is valkey support planned for the future? #297

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Question (redis-ha): is valkey support planned for the future? #297

Description

Activity

DandyDeveloper commented on Oct 24, 2024

maxisam commented on Apr 1, 2025

pierluigilenoci commented on Sep 15, 2025

DandyDeveloper commented on Sep 15, 2025

mveroone commented on Sep 18, 2025

erolclk1 commented on Jan 22, 2026

DandyDeveloper commented on Jan 23, 2026

Sven1410 commented on Jan 23, 2026

bootc commented on Feb 10, 2026

flamein commented on Feb 13, 2026

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions