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. The Upgrade notes column says whether a release has anything else to know before you upgrade.

If you deploy Redpanda with the Redpanda Operator, see Redpanda Operator Release Notes instead. To check which versions of Redpanda, Kubernetes, and Helm each release supports, see Kubernetes Compatibility.

Version Highlights Upgrade notes

v26.3.1
2026-11-20

Gateway API TLSRoute support for external access is now GA, brokers can listen on an IPv6 address, and the chart deploys Redpanda v26.3.1 by default.

Yes

v26.3.1 (2026-11-20)

Gateway API TLSRoute support for external access is now GA, brokers can listen on an IPv6 address, and the chart deploys Redpanda v26.3.1 by default.

Before you upgrade
  • Upgrading an existing release changes the Pod template, so the brokers restart.

  • If you override the configurator or fs-validator volumes or volumeMounts through podTemplate, re-key the override from the old <fullname>-configurator or <fullname>-fs-validator name to configurator or fs-validator. An override keyed on the old name silently stops matching.

  • The default Redpanda version installed by the chart changes to v26.3.1, and the bundled Console subchart deploys Redpanda Console v3.15.0 by default.

  • Without a license configured, Redpanda v26.3 and later refuse to start a broker that is upgrading to the next feature release when the brokers' cores total more than 50. Brokers that set no CPU use every core on their nodes.

  • The chart no longer checks image.tag for compatibility, so a Redpanda version older than the chart supports fails at runtime instead of at render time. The force value no longer has any effect.

  • listeners.<api>.external.<listener-name>.nodePort has no effect. The LoadBalancer Service publishes the first entry of advertisedPorts, or the port of the listener if advertisedPorts is empty.

  • For an external listener without advertisedPorts or nodePort, the LoadBalancer Service port changes to the port of the listener, to match the port the broker advertises.

  • Brokers with a trustStore on an internal Admin API, Kafka API, or Schema Registry listener restart once on upgrade.

Install or upgrade to this version
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda redpanda/redpanda \
  --namespace <namespace> \
  --create-namespace \
  --version 26.3.1 \
  --values <values-file>

This chart deploys Redpanda v26.3.1 by default. Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade Redpanda in Kubernetes.

New features

  • The address value of a listener overrides the address that Redpanda listens on, so a broker can listen on the IPv6 address :: instead of the IPv4-only default 0.0.0.0.

  • The commonAnnotations value adds the given annotations to every object the chart renders, including the StatefulSet, for example argocd.argoproj.io/sync-wave: "1". The StatefulSet’s Pod template and volume claim templates are left unannotated, and annotations set on an individual resource take precedence.

  • Without a license configured, the post-install notes warn when the brokers' cores total more than 50, or when the brokers set no CPU and so use every core on their nodes. Past 50 cores, Redpanda v26.3 and later refuse to start a broker that is upgrading to the next feature release.

Improvements

  • The configurator and fs-validator script volumes on the Redpanda StatefulSet are now named configurator and fs-validator rather than <fullname>-configurator and <fullname>-fs-validator, which keeps the configurator volume name within the Kubernetes 63 character limit for releases with a long fullname. Upgrading restarts the brokers, and a podTemplate override keyed on an old volume name must be re-keyed to the new name.

  • LoadBalancer Services now also carry a correctly spelled redpanda.com/type: loadbalancer label, and the post-install notes select on it. The misspelled repdanda.com/type label is still set for existing selectors.

  • values.schema.json is now 3-5x smaller, which reduces the time that every helm template, helm install, and helm upgrade spends compiling it. The schema accepts the same values as before, except that arrays nested inside a list or map of objects, such as podTemplate.spec.containers[].args, now accept null as well as a list.

  • Every Service port the chart renders now carries appProtocol, if specified, and an explicit targetPort. The change is inert to Kubernetes, but applying it rewrites the Services.

  • Gateway API TLSRoute support for external access is now GA. The listeners.<proto>.external.<name>.type: tlsroute and external.gateway values are stable and no longer subject to backwards-incompatible changes.

  • The bundled Console subchart now deploys Redpanda Console v3.15.0 by default.

  • The default Redpanda version installed by the chart is now v26.3.1.

  • The operator sidecar image tag is now v26.3.1.

Bug fixes

  • The preStop lifecycle hook no longer stalls Pod termination or sends SIGTERM to a broker that is still draining. The hook now skips the drain for a broker whose node ID is no longer a cluster member, and every Admin API call it makes has a timeout.

  • The sidecar no longer momentarily revokes superuser status from connected clients when it starts or when a users Secret is updated. This issue affected only Helm chart deployments, not clusters deployed by the operator.

  • The sidecar now writes the superusers cluster property only when the list changes, so sidecar restarts no longer bump the cluster config version. When a users file can’t be read, the sidecar retries instead of writing a partial list.

  • Malformed lines in a users file, which can contain passwords, are no longer written to the sidecar log.

  • resources.memory.container no longer shows the memory locking description in the Helm reference. That description belongs to resources.memory.enable_memory_locking.

  • The resources.memory.enable_memory_locking description no longer says to set it to true for production. It now describes what memory locking does and when it applies.

  • A broker configured with listeners.rpc.tls.trustStore now starts. The RPC listener’s trustStore is now projected into the truststores volume. Previously, rpc_server_tls.truststore_file named a path that nothing mounted.

  • helm install prints the post-install notes again.

  • The mTLS instructions in the post-install notes now reference the Secrets that the chart creates or the configured secretRef or clientSecretRef, with one client certificate fetch for each listener that requires client auth. Previously, they referenced the <fullname>-client Secret, which the chart no longer generates.

  • The LoadBalancer address remediation command in the post-install notes now targets the installed release name instead of the chart name, and reads only this release’s LoadBalancer Services.

  • The SASL credential setup in the post-install notes now works in bash. Previously, the variables were discarded before the export.

  • With more than one external Kafka, Admin API, or Schema Registry listener, the rpk profile ConfigMap and the advertised ports now use the alphabetically first listener when rendered with helm template or helm install. Previously, the choice depended on map iteration order.

  • An external listener with enabled: false is no longer advertised. Previously, the chart advertised an address for a listener that Redpanda was never told to bind.

  • config.rpk.tune_*: false is honored again when tuning.apply_host_tuners is enabled. Previously, every default-enabled tuner ran regardless of the opt-out.

  • Client Certificate resources now respect tls.certs.<name>.issuerRef.group. Previously, the group was forced to cert-manager.io, so with an external issuer and requireClientAuth: true, the client Certificate was never issued.

  • With tls.certs.<name>.caEnabled: false, the CA reference that the chart provides to the operator and Console now points at the serving certificate’s tls.crt. Previously, it pointed at a nonexistent cert.crt key, so those clients couldn’t verify the cluster.

  • When the Admin API listener sets requireClientAuth: true, the StatefulSet’s Admin API curl calls now verify the server with the listener’s trustStore or the server certificate’s CA. Previously, they always used ca.crt from the client certificate’s Secret.

  • The LoadBalancer Service port for an external listener without advertisedPorts or nodePort is now the port of the listener. Previously, it was the in-cluster port of the API, which did not match the port the broker advertised, so clients could not connect.

  • ClusterRole and ClusterRoleBinding names are no longer truncated to 63 characters. Previously, when <fullname>-<namespace> reached that limit, every ClusterRole rendered under the same name and overwrote the others' rules.

  • A broker is no longer left in maintenance mode after a rolling restart when its Admin API takes longer than half the termination grace period (45s by default) to start. Previously, that broker held no partition leadership and prevented the next broker in the roll from being drained before its restart.

  • Clients in the broker Pods, including rpk, the sidecar, the lifecycle hooks, and the post-install Job, now verify an internal Admin API, Kafka API, or Schema Registry listener that has a trustStore, including when the listener’s certificate also has a CA (caEnabled). Brokers with a trustStore on one of these listeners restart once on upgrade.

Deprecations

  • The misspelled repdanda.com/type label on LoadBalancer Services will be removed in the next major release.

Removed

  • The chart no longer checks image.tag for compatibility. Deploying a Redpanda version older than the chart supports now fails at runtime instead of with a render-time error, and the force value no longer has any effect.

  • redpanda.yaml no longer sets admin_api_tls, kafka_api_tls, pandaproxy_api_tls, and schema_registry_api_tls to explicit nulls when no listener on that API serves TLS. The keys are now omitted.

  • listeners.<api>.external.<listener-name>.nodePort has no effect. The LoadBalancer Service now publishes the first entry of advertisedPorts, or the port of the listener if advertisedPorts is empty.