[NEW] Valkey chart dependency on Bitnami

[GiedriusMal]

Hi team,

I wanted to raise a concern regarding the recommended official installation method for Valkey via the Using Bitnami's Valkey chart. While using Helm is convenient on Kubernetes environments—the tight dependency on Bitnami creates a bottleneck in time-sensitive situations like critical CVEs or urgent updates.

Example:

• Official Valkey

  8.1.1 Latest released this 2 weeks ago
  Security fixes
  (CVE-2025-21605) Limit output buffer for unauthenticated client

• Bitnami Valkey chart

  App version: 8.1.1.
  Chart version: 3.0.3.
  merged 2 commits into [main] last week [bitnami/valkey] Release 3.0.3 bitnami/charts#33219

In such cases, we are forced to wait for Bitnami to publish a patched version of the chart and container, which makes delays in critical security fixes, in example above, it took almost a week.

Questions / Suggestions:

• Is there a plan to provide an official Valkey Helm chart or container image outside of Bitnami?
• Could the Valkey project support or maintain its own Helm chart repo to reduce this dependency?
• Alternatively, could documentation be improved to help users more easily fork and maintain their own chart if needed?

Any option would benefit Valkey and the community. Thank you for all your work and will wait for responses. Thanks in advance.

Giedrius

[zuiderkwast]

@rafariossaa

[GiedriusMal]

Any updates?

[zuiderkwast]

Valkey maintainers don't specifically recomment bitnami charts. This is one bloggers opinion.

The blog is in the website repo https://github.com/valkey-io/valkey-io.github.io. I'm going to transfer this issue to that repo.

Feel free to edit his blogpost and add some notes about it. It's just markdown in a git repo.

[stockholmux]

So, it looks like @rafariossaa no longer works for Bitnami, so no surprise that he isn't responding.

Blogs represent a slice-in-time and at a specific viewpoint of an author. The docs are more definitive advice, blogs aren't docs though.

I agree with @zuiderkwast: if you think this is important, feel free to add a note to the blog post.

[rafariossaa]

Hi,
Sorry for the very late response.
Yes, I not longer work for Bitnami (from Aug 2024).
If your concern is about how long it takes usually it is pretty quick. They are done mostly automatically. Maybe in this case there was something that didn't work automatically and needed someone to take a look to it.
Also, I know some policies have changed on regard what is public and what is not, perhaps this also affect the frequency.
In any case, I would suggest to open a issue on bitnami chart repository.. They review issues on a daily basis and they will do their best to provide feedback and a solution.