--- title: Valkey · Valkey Helm: The new way to deploy Valkey on... description: An official, project-maintained Helm chart for Valkey now exists as an alternative to Bitnami charts, whose image and licensing policies changed and caused... canonical: https://daily.dev/posts/valkey-valkey-helm-the-new-way-to-deploy-valkey-on-kubernetes-gw4rtomzc twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Valkey · Valkey Helm: The new way to deploy Valkey on Kubernetes | daily.dev og:description: An official, project-maintained Helm chart for Valkey now exists as an alternative to Bitnami charts, whose image and licensing policies changed and caused... og:url: https://daily.dev/posts/valkey-valkey-helm-the-new-way-to-deploy-valkey-on-kubernetes-gw4rtomzc og:image: https://api.daily.dev/og/posts/Gw4RtoMZC.png og:image:alt: Valkey · Valkey Helm: The new way to deploy Valkey on Kubernetes og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Valkey · Valkey Helm: The new way to deploy Valkey on Kubernetes **[Valkey](https://daily.dev/sources/valkey-blog)** · 7 min read · 0 upvotes · 0 comments ## Summary An official, project-maintained Helm chart for Valkey now exists as an alternative to Bitnami charts, whose image and licensing policies changed and caused deployment issues like ImagePullBackOff errors and cluster drift. The new chart supports standalone and replicated topologies, ACL-based auth, TLS, and Prometheus metrics. Since the Bitnami and official charts use incompatible resource naming and structures, in-place upgrades aren't possible; instead a step-by-step migration path is provided: deploy the new chart alongside the existing one, replicate data, fail over during a maintenance window, then switch clients to the new endpoints. Planned future features include Sentinel-based high availability, more persistence control, and Cluster support. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I migrate my Valkey deployment from the Bitnami Helm chart to the official Valkey Helm chart on Kubernetes? Deploy the official valkey-io/valkey-helm chart alongside the existing Bitnami installation using a new instance name, then enable replication by pointing the new instance at the current primary with replicaof. During a brief maintenance window, pause writes, run failover to promote the new instance to primary, then switch clients to the new read-write and read-only service endpoints. In-place upgrade is not possible because the charts use incompatible naming conventions and resource structures. _daily.dev surfaces migration guides like this for teams planning a Valkey or Redis infrastructure change._ ### Why did Bitnami Helm charts start causing ImagePullBackOff errors and failed rollouts in production Kubernetes clusters? Bitnami changed how it publishes and supports many container images and Helm charts, moving some images behind new terms so older tags are no longer available as before. This causes rollouts to fail with ImagePullBackOff or auth and 404 errors, clusters to drift when staging keeps cached images while production can't pull a different tag, and rollbacks to fail because the old image is unfetchable. _Track vendor policy shifts like this on daily.dev before they break your deployment pipelines._ ### What features does the official Valkey Helm chart support for Kubernetes deployments? It supports standalone instances with optional persistence, primary-replica topology with separate read and read-write endpoints, ACL-based authentication with fine-grained user permissions, TLS encryption for client-server and replica-primary communication, and Prometheus metrics via an exporter. Planned additions include Sentinel-based high availability, more persistence control, and Cluster support, tracked in the chart's GitHub milestones. _Compare Helm chart capabilities like these on daily.dev when choosing how to run Valkey in production._ ## Similar posts on daily.dev - [Valkey · Valkey Metrics in Prometheus: redis](https://daily.dev/posts/valkey-valkey-metrics-in-prometheus-redis-93jg7u5j6) · Valkey · 1 upvotes · 0 comments - [Valkey just had a 17x year. Its lead maintainer still doesn’t want Redis to die.](https://daily.dev/posts/valkey-just-had-a-17x-year-its-lead-maintainer-still-doesn-t-want-redis-to-die--hymzgle9p) · The New Stack · 2 upvotes · 0 comments - [Valkey · Monitoring Valkey with Prometheus](https://daily.dev/posts/valkey-monitoring-valkey-with-prometheus-glygpdnfc) · Valkey · 1 upvotes · 0 comments - [Using Valkey on Azure and in .NET Aspire](https://daily.dev/posts/using-valkey-on-azure-and-in-net-aspire-8hoh4cisd) · InfoWorld · 0 upvotes · 0 comments - [Grafana's Kubernetes Monitoring Helm Chart v4 Brings Multiple Fixes](https://daily.dev/posts/grafana-s-kubernetes-monitoring-helm-chart-v4-brings-multiple-fixes-jxmbzpkpe) · InfoQ · 5 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#redis](https://daily.dev/tags/redis), [#helm](https://daily.dev/tags/helm), [#valkey](https://daily.dev/tags/valkey) [View this post on daily.dev](https://daily.dev/posts/valkey-valkey-helm-the-new-way-to-deploy-valkey-on-kubernetes-gw4rtomzc) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Valkey · Valkey Helm: The new way to deploy Valkey on Kubernetes","url":"https://daily.dev/posts/valkey-valkey-helm-the-new-way-to-deploy-valkey-on-kubernetes-gw4rtomzc","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/valkey-valkey-helm-the-new-way-to-deploy-valkey-on-kubernetes-gw4rtomzc"},"datePublished":"2026-08-23T12:22:04.165Z","dateModified":"2026-08-23T12:46:53.835Z","description":"An official, project-maintained Helm chart for Valkey now exists as an alternative to Bitnami charts, whose image and licensing policies changed and caused...","image":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","thumbnailUrl":"https://media.daily.dev/image/upload/s--CxzD6vbw--/f_auto/v1722860399/public/Placeholder%2005","isAccessibleForFree":true,"articleSection":"Valkey","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Valkey","logo":"https://media.daily.dev/image/upload/s--XXPzEmD8--/f_auto,q_auto/v1787487496/logos/valkey-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/valkey-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/valkey-valkey-helm-the-new-way-to-deploy-valkey-on-kubernetes-gw4rtomzc","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,redis,helm,valkey","timeRequired":"PT7M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Valkey","item":"https://daily.dev/sources/valkey-blog"},{"@type":"ListItem","position":3,"name":"Valkey · Valkey Helm: The new way to deploy Valkey on Kubernetes"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/valkey-valkey-helm-the-new-way-to-deploy-valkey-on-kubernetes-gw4rtomzc#faq","mainEntity":[{"@type":"Question","name":"How do I migrate my Valkey deployment from the Bitnami Helm chart to the official Valkey Helm chart on Kubernetes?","acceptedAnswer":{"@type":"Answer","text":"Deploy the official valkey-io/valkey-helm chart alongside the existing Bitnami installation using a new instance name, then enable replication by pointing the new instance at the current primary with replicaof. During a brief maintenance window, pause writes, run failover to promote the new instance to primary, then switch clients to the new read-write and read-only service endpoints. In-place upgrade is not possible because the charts use incompatible naming conventions and resource structures. daily.dev surfaces migration guides like this for teams planning a Valkey or Redis infrastructure change."}},{"@type":"Question","name":"Why did Bitnami Helm charts start causing ImagePullBackOff errors and failed rollouts in production Kubernetes clusters?","acceptedAnswer":{"@type":"Answer","text":"Bitnami changed how it publishes and supports many container images and Helm charts, moving some images behind new terms so older tags are no longer available as before. This causes rollouts to fail with ImagePullBackOff or auth and 404 errors, clusters to drift when staging keeps cached images while production can't pull a different tag, and rollbacks to fail because the old image is unfetchable. Track vendor policy shifts like this on daily.dev before they break your deployment pipelines."}},{"@type":"Question","name":"What features does the official Valkey Helm chart support for Kubernetes deployments?","acceptedAnswer":{"@type":"Answer","text":"It supports standalone instances with optional persistence, primary-replica topology with separate read and read-write endpoints, ACL-based authentication with fine-grained user permissions, TLS encryption for client-server and replica-primary communication, and Prometheus metrics via an exporter. Planned additions include Sentinel-based high availability, more persistence control, and Cluster support, tracked in the chart's GitHub milestones. Compare Helm chart capabilities like these on daily.dev when choosing how to run Valkey in production."}}]} ```