Add blog post: Introduction to Valkey helm chart #408
Conversation
Signed-off-by: cherukum-amazon <cherukum@amazon.com>
cherukum-Amazon
requested review from
madolson and
stockholmux
as code owners
stockholmux
left a comment
stockholmux
left a comment
There was a problem hiding this comment.
I like the blog! It has some usability issues with the code samples but they should be pretty easy to fix.
Otherwise, it's just little things that need attention. With the fixes, I think we can publish next week if you can get to the changes required ASAP.
| title = "Valkey Helm: The new way to deploy Valkey on Kubernetes" | ||
| date = 2025-11-05 | ||
| description = "A guide on why the new Valkey Helm chart exists, how it helps, and how to migrate from Bitnami." | ||
| author = ["maheshcherukumilli"] |
There was a problem hiding this comment.
Your bio isn't showing so change 'author' to 'authors'
| featured_image = "/assets/media/featured/valkey-helm.webp" | ||
| +++ | ||
|
|
||
| ## Bitnami changes and why it matters |
There was a problem hiding this comment.
This doesn't follow proper heading/content hierarchy. Each heading needs to have content immediately following it, not another heading.
I would just remove the h2 here and go directly into the next paragraph.
|
|
||
| ## Bitnami changes and why it matters | ||
|
|
||
| Bitnami is changing how it publishes and supports many container images and Helm charts (**see [charts issue #35164](https://github.com/bitnami/charts/issues/35164), [charts issue #36215](https://github.com/bitnami/charts/issues/36215), and the [Bitnami Secure Images announcement](https://news.broadcom.com/app-dev/broadcom-introduces-bitnami-secure-images-for-production-ready-containerized-applications)**). Some images move behind new terms, and older tags may not be available as before. If your pipelines pull Bitnami charts or images during deploys, you can see rollouts fail (ImagePullBackOff, auth/404), clusters drift (staging keeps old cached bits while prod can’t pull or resolves a different tag), and “invisible” upgrades when a moved tag points to a new digest. During incidents, rollbacks slow down or fail because the old image isn’t fetchable. Compliance can break, security patches can stall behind limits or paywalls, and you may face surprise licensing or mirroring costs. Net effect: slower releases, harder debugging, inconsistent environments, and higher operational and business risk. |
There was a problem hiding this comment.
unbold the parenthetical starting with "see"
There was a problem hiding this comment.
put ImagePullBackOff in backticks e.g. ImagePullBackOff
|
|
||
| Bitnami is changing how it publishes and supports many container images and Helm charts (**see [charts issue #35164](https://github.com/bitnami/charts/issues/35164), [charts issue #36215](https://github.com/bitnami/charts/issues/36215), and the [Bitnami Secure Images announcement](https://news.broadcom.com/app-dev/broadcom-introduces-bitnami-secure-images-for-production-ready-containerized-applications)**). Some images move behind new terms, and older tags may not be available as before. If your pipelines pull Bitnami charts or images during deploys, you can see rollouts fail (ImagePullBackOff, auth/404), clusters drift (staging keeps old cached bits while prod can’t pull or resolves a different tag), and “invisible” upgrades when a moved tag points to a new digest. During incidents, rollbacks slow down or fail because the old image isn’t fetchable. Compliance can break, security patches can stall behind limits or paywalls, and you may face surprise licensing or mirroring costs. Net effect: slower releases, harder debugging, inconsistent environments, and higher operational and business risk. | ||
|
|
||
| To reduce the impact on Valkey deployments, the community created an official, project-owned Helm chart (**request: [issue #2371](https://github.com/valkey-io/valkey/issues/2371)**, **chart: [valkey-helm](https://github.com/valkey-io/valkey-helm)**). With the official chart, you can pin chart and image versions, keep `values.yaml` in code, and upgrade on your schedule without depending on vendor policy changes. |
There was a problem hiding this comment.
unbold the parenthetical starting with "request"
There was a problem hiding this comment.
"owned" is a weird word in open source. Maybe 'project-maintained' ?
|
|
||
| ### Why a Valkey maintained chart helps | ||
|
|
||
| With the official chart, you run what you intend, not what a third party changes. Pin a chart release from the Valkey repo (for example `--version 0.7.7` from [https://github.com/valkey-io/valkey-helm](https://github.com/valkey-io/valkey-helm)) and lock the Valkey image tag in your `values.yaml`. Because the chart follows Valkey releases and docs, you can bump versions in a pull request, test in staging, then promote the same versions to production. If something breaks, use Helm history to roll back with `helm rollback <release> <revision>`. Keep your values in source control, often per environment (`values.staging.yaml`, `values.prod.yaml`), and you get a clean GitOps flow. For details and examples, see the README: https://github.com/valkey-io/valkey-helm#readme. |
There was a problem hiding this comment.
Avoid using a raw URLs and link the README
Although I think the raw URL makes sense for the 0.7.7 example.
|
|
||
| ## Next steps | ||
|
|
||
| This is the rough plan. We will keep the work visible in the repo at [https://github.com/valkey-io/valkey-helm](https://github.com/valkey-io/valkey-helm). |
There was a problem hiding this comment.
Why is this a rough plan? What does that mean?
Shorten the link to text to valkey-io/valkey-helm
There was a problem hiding this comment.
Change 'We will keep the work visible in the repo' to something like 'All development on this Helm chart occurs in the open'.
(The future tense isn't correct in the original and I like to avoid conusing 'we' statements).
|
|
||
| This is the rough plan. We will keep the work visible in the repo at [https://github.com/valkey-io/valkey-helm](https://github.com/valkey-io/valkey-helm). | ||
|
|
||
| * **Cluster mode.** Make it easy to run primaries and replicas across slots with sane defaults. |
There was a problem hiding this comment.
Do any of these have links to issues?
| * **Upgrades.** Publish notes tied to Valkey releases. Add hooks and checks so failures are obvious and quick to revert. | ||
| * **Docs.** Keep them short. Add clear examples. Link to deeper guides only when needed. | ||
|
|
||
| If you currently rely on Bitnami, test this chart in a dev cluster and try your normal workflows. If something is missing, open an issue at [https://github.com/valkey-io/valkey-helm/issues](https://github.com/valkey-io/valkey-helm/issues). Once you try out the official Valkey helm chart please share feedback so the chart grows in the right direction. |
There was a problem hiding this comment.
change the link text to 'valkey-io/valkey-helm'
| * **Docs.** Keep them short. Add clear examples. Link to deeper guides only when needed. | ||
|
|
||
| If you currently rely on Bitnami, test this chart in a dev cluster and try your normal workflows. If something is missing, open an issue at [https://github.com/valkey-io/valkey-helm/issues](https://github.com/valkey-io/valkey-helm/issues). Once you try out the official Valkey helm chart please share feedback so the chart grows in the right direction. | ||
|
|
There was a problem hiding this comment.
ditch the extra lines at the end please
There was a problem hiding this comment.
something is wonky with the horizontal spacing. The plus sign is centred perfectly but the helm logo is far closer to the right side of the plus than the valkey logo is to the left side of the plus.
Also each blue is every so slightly different.
2 participants
Description
Description
This pull request adds a new blog post titled “Valkey Helm: The new way to deploy Valkey on Kubernetes”.
The blog explains why the Valkey project now provides an official Helm chart, summarizes recent Bitnami changes affecting users, and provides a detailed step-by-step migration guide for moving from Bitnami’s Valkey chart to the official Valkey chart.
The post includes:
This helps users adopt the official Helm chart safely and confidently.
Issues Resolved
This PR contributes toward addressing the community request for an official Helm chart and supporting documentation.
It provides the end-to-end migration guidance referenced in:
valkey-io/valkey#2371 (request for an official Helm chart)
Check List
--signoffBy submitting this pull request, I confirm that my contribution is made under the terms of the BSD-3-Clause License.