[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.