Redpanda Helm Chart Release Notes
This page lists the changes in each Redpanda Helm chart release in this release line, newest first. Each release shows what to know before you upgrade and the command to upgrade to that version.
Every chart release changes the operator sidecar image that runs in the broker Pods, so upgrading the chart restarts all brokers in a rolling restart.
If you deploy Redpanda with the Redpanda Operator, see Redpanda Operator Release Notes instead. For a summary of the major features in this release line, see What’s New in the Helm Charts. To check which versions of Redpanda, Kubernetes, and Helm each release supports, see Kubernetes Compatibility.
| Version | Highlights | Upgrade notes |
|---|---|---|
v26.1.15 |
The default Redpanda version installed by the chart is now v26.1.21, and the operator sidecar image tag is now v26.1.15. |
|
v26.1.14 |
Clients in the broker Pods now verify a listener that has a |
|
v26.1.13 |
The default Redpanda version and the operator sidecar image no longer trust the compromised eMudhra certificate authorities (CVE-2026-111943), and |
|
v26.1.12 |
|
No |
v26.1.11 |
Connected clients no longer lose superuser status for a moment when the sidecar starts, and the default Redpanda version is now v26.1.17. |
|
v26.1.10 |
The default Redpanda version is now v26.1.14, and the |
|
v26.1.9 |
Upgrades with SASL enabled no longer fail under Helm 4’s default server-side apply. |
No |
v26.1.8 |
The bundled Console subchart moves to v3.8.0. |
No |
v26.1.7 |
Boolean cluster properties set to |
|
v26.1.6 |
The operator sidecar image moves to the v26.1.6 release. |
No |
v26.1.5 |
The operator sidecar image tag moves to v26.1.5. |
No |
v26.1.4 |
The default Redpanda version is now v26.1.8, and the |
|
v26.1.3 |
Ballast file tuning now propagates the ballast file to the main container, SCRAM authentication no longer fails when the bootstrap user password comes from an externally managed Secret, and the default Redpanda version is now v26.1.6. |
|
v26.1.2 |
Post-upgrade processing of cluster configuration no longer fails on properties removed between Redpanda versions, and configuration job Pods no longer share labels with StatefulSet Pods. |
No |
v26.1.1 |
External listeners can use TLS when the internal listener does not, the chart’s containers get stricter security contexts, and the chart installs 26.1.1 releases by default. |
v26.1.15 (2026-11-20)
The default Redpanda version installed by the chart is now v26.1.21, and the operator sidecar image tag is now v26.1.15.
|
Before you upgrade
|
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.15 \
--values <values-file>
This chart deploys Redpanda v26.1.21 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
v26.1.14 (2026-11-11)
Clients in the broker Pods now verify a listener that has a trustStore, a disabled external listener is no longer advertised, and the default Redpanda version is now v26.1.20.
|
Before you upgrade
|
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.14 \
--values <values-file>
This chart deploys Redpanda v26.1.20 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
Improvements
-
The bundled Console subchart now deploys Redpanda Console v3.14.0 by default.
-
The default Redpanda version installed by the chart is now v26.1.20.
-
The operator sidecar image tag is now v26.1.14.
Bug fixes
-
Clients in the broker Pods, including
rpk, the sidecar, and the post-install Job, now verify an internal Admin API, Kafka API, or Schema Registry listener that has atrustStore. Brokers with atrustStoreon one of these listeners restart once on upgrade.Details
The sidecar and the post-install Job now mount the trust stores, so they can connect to the Admin API. If the listener’s certificate also has a CA (
caEnabled), clients now verify it with a bundle ofca.crtand the trust store. Previously, they used the trust store alone, which failed if it held only client CAs, and thepostStarthook then retried forever. A broker keeps verifying with the trust store alone until it restarts. -
An external Kafka or HTTP listener with
enabled: falseis no longer advertised. Previously, the configurator wrote an advertised address for the disabled listener, which Redpanda was never told to bind.
v26.1.13 (2026-10-23)
The default Redpanda version and the operator sidecar image no longer trust the compromised eMudhra certificate authorities (CVE-2026-111943), and values.schema.json is 3-5x smaller.
|
Before you upgrade
|
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.13 \
--values <values-file>
This chart deploys Redpanda v26.1.19 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
Improvements
-
values.schema.jsonis now 3-5x smaller, which reduces what everyhelm template,helm install, andhelm upgradecompiles. The schema accepts the same values as before, with one exception: arrays nested inside a list or map of objects (for examplepodTemplate.spec.containers[].args) now acceptnullas well as a list. -
The default Redpanda version installed by the chart is now v26.1.19, whose image no longer trusts the compromised eMudhra certificate authorities (CVE-2026-111943).
-
The operator sidecar image tag is now v26.1.13, which is built with Go 1.26.10 and rejects certificates chaining to the compromised eMudhra certificate authorities (CVE-2026-111943).
v26.1.12 (2026-09-24)
helm install prints the post-install notes again, and the operator sidecar image tag moves to v26.1.12.
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.12 \
--values <values-file>
This chart deploys Redpanda v26.1.17 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
v26.1.11 (2026-09-03)
Connected clients no longer lose superuser status for a moment when the sidecar starts, and the default Redpanda version is now v26.1.17.
|
Before you upgrade
|
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.11 \
--values <values-file>
This chart deploys Redpanda v26.1.17 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
Improvements
-
The operator sidecar image tag is now v26.1.11.
-
The default Redpanda version installed by the chart is now v26.1.17.
Bug fixes
-
Connected clients no longer lose superuser status for a moment when the sidecar starts or a users Secret is updated. This issue affected only Helm chart deployments.
-
The sidecar now sets the
superuserscluster property only when the list changes, so sidecar restarts no longer bump the cluster config version. Malformed users-file lines, which can contain passwords, are no longer written to the sidecar log.
v26.1.10 (2026-07-29)
The default Redpanda version is now v26.1.14, and the postStart lifecycle hook clears maintenance mode left behind by a Pod that re-registered under a different node ID.
|
Before you upgrade
|
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.10 \
--values <values-file>
This chart deploys Redpanda v26.1.14 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
Improvements
-
The default Redpanda version installed by the chart is now v26.1.14.
-
The operator sidecar image tag is now v26.1.10.
Bug fixes
-
The
postStartlifecycle hook now clears maintenance mode left behind by a Pod that re-registered under a different node ID, for example after losing its data directory when running without persistent storage. Previously, the old node ID stayed in maintenance mode forever, which blocked every other broker from entering maintenance mode and excluded the old broker from the partition autobalancer’s auto-decommission (partition_autobalancing_node_autodecommission_timeout_sec). The hook clears only node IDs that the cluster reports as dead and draining. A normal restart that keeps its node ID is unaffected.
v26.1.9 (2026-07-14)
Upgrades with SASL enabled no longer fail under Helm 4’s default server-side apply.
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.9 \
--values <values-file>
This chart deploys Redpanda v26.1.12 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
v26.1.8 (2026-07-06)
The bundled Console subchart moves to v3.8.0.
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.8 \
--values <values-file>
This chart deploys Redpanda v26.1.12 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
v26.1.7 (2026-06-30)
Boolean cluster properties set to false under config.cluster now take effect when Tiered Storage defaults apply, and the default Redpanda version is v26.1.12.
|
Before you upgrade
|
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.7 \
--values <values-file>
This chart deploys Redpanda v26.1.12 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
v26.1.6 (2026-06-17)
The operator sidecar image moves to the v26.1.6 release.
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.6 \
--values <values-file>
This chart deploys Redpanda v26.1.8 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
v26.1.5 (2026-06-04)
The operator sidecar image tag moves to v26.1.5.
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.5 \
--values <values-file>
This chart deploys Redpanda v26.1.8 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
v26.1.4 (2026-05-26)
The default Redpanda version is now v26.1.8, and the ServiceMonitor renders a lowercase scheme that older prometheus-operator CRDs accept.
|
Before you upgrade
|
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.4 \
--values <values-file>
This chart deploys Redpanda v26.1.8 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
v26.1.3 (2026-04-24)
Ballast file tuning now propagates the ballast file to the main container, SCRAM authentication no longer fails when the bootstrap user password comes from an externally managed Secret, and the default Redpanda version is now v26.1.6.
|
Before you upgrade
|
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.3 \
--values <values-file>
This chart deploys Redpanda v26.1.6 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
Bug fixes
-
Ballast file tuning now propagates the ballast file to the main container. Previously, the tuning container did not mount the directory it needed.
-
The bootstrap user password is now loaded from an externally managed Secret referenced through
auth.sasl.bootstrapUser.secretKeyRef. Previously, SCRAM authentication failed from the operator and other chart-owned clients.
v26.1.2 (2026-04-03)
Post-upgrade processing of cluster configuration no longer fails on properties removed between Redpanda versions, and configuration job Pods no longer share labels with StatefulSet Pods.
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.2 \
--values <values-file>
This chart deploys Redpanda v26.1.1 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
Bug fixes
-
Post-upgrade processing of cluster configuration no longer results in configuration errors caused by properties that were removed between Redpanda versions.
-
Configuration job Pods now have labels that do not overlap with the labels of StatefulSet Pods, so selectors used elsewhere no longer match the job Pods.
v26.1.1 (2026-04-01)
External listeners can use TLS when the internal listener does not, the chart’s containers get stricter security contexts, and the chart installs 26.1.1 releases by default.
|
Before you upgrade
|
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
--namespace <namespace> \
--create-namespace \
--version 26.1.1 \
--values <values-file>
This chart deploys Redpanda v26.1.1 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.
New features
-
TLS can be enabled on external listeners independently of the internal listener’s TLS state. External sub-listener TLS certificates are now mounted even when the internal listener has TLS disabled.
-
The security contexts of the redpanda, redpanda-configurator, and sidecar containers set
allowPrivilegeEscalation: falseandrunAsNonRoot: true. This addresses GKE security findings.