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 |
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. |
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
|
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
commonAnnotationsvalue adds the given annotations to every object the chart renders, including the StatefulSet, for exampleargocd.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
configuratorandfs-validatorrather than<fullname>-configuratorand<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 apodTemplateoverride 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: loadbalancerlabel, and the post-install notes select on it. The misspelledrepdanda.com/typelabel is still set for existing selectors. -
values.schema.jsonis now 3-5x smaller, which reduces the time that everyhelm template,helm install, andhelm upgradespends compiling it. The schema accepts the same values as before, except that arrays nested inside a list or map of objects, such aspodTemplate.spec.containers[].args, now acceptnullas well as a list. -
Every Service port the chart renders now carries
appProtocol, if specified, and an explicittargetPort. 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: tlsrouteandexternal.gatewayvalues 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
preStoplifecycle 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
superuserscluster 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.containerno longer shows the memory locking description in the Helm reference. That description belongs toresources.memory.enable_memory_locking. -
The
resources.memory.enable_memory_lockingdescription no longer says to set it totruefor production. It now describes what memory locking does and when it applies. -
A broker configured with
listeners.rpc.tls.trustStorenow starts. The RPC listener’strustStoreis now projected into thetruststoresvolume. Previously,rpc_server_tls.truststore_filenamed a path that nothing mounted. -
helm installprints the post-install notes again. -
The mTLS instructions in the post-install notes now reference the Secrets that the chart creates or the configured
secretReforclientSecretRef, with one client certificate fetch for each listener that requires client auth. Previously, they referenced the<fullname>-clientSecret, 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
rpkprofile ConfigMap and the advertised ports now use the alphabetically first listener when rendered withhelm templateorhelm install. Previously, the choice depended on map iteration order. -
An external listener with
enabled: falseis no longer advertised. Previously, the chart advertised an address for a listener that Redpanda was never told to bind. -
config.rpk.tune_*: falseis honored again whentuning.apply_host_tunersis enabled. Previously, every default-enabled tuner ran regardless of the opt-out. -
Client
Certificateresources now respecttls.certs.<name>.issuerRef.group. Previously, the group was forced tocert-manager.io, so with an external issuer andrequireClientAuth: 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’stls.crt. Previously, it pointed at a nonexistentcert.crtkey, so those clients couldn’t verify the cluster. -
When the Admin API listener sets
requireClientAuth: true, the StatefulSet’s Admin APIcurlcalls now verify the server with the listener’strustStoreor the server certificate’s CA. Previously, they always usedca.crtfrom the client certificate’s Secret. -
The LoadBalancer Service port for an external listener without
advertisedPortsornodePortis 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. -
ClusterRoleandClusterRoleBindingnames are no longer truncated to 63 characters. Previously, when<fullname>-<namespace>reached that limit, everyClusterRolerendered 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 atrustStore, including when the listener’s certificate also has a CA (caEnabled). Brokers with atrustStoreon one of these listeners restart once on upgrade.
Deprecations
-
The misspelled
repdanda.com/typelabel on LoadBalancer Services will be removed in the next major release.
Removed
-
The chart no longer checks
image.tagfor compatibility. Deploying a Redpanda version older than the chart supports now fails at runtime instead of with a render-time error, and theforcevalue no longer has any effect. -
redpanda.yamlno longer setsadmin_api_tls,kafka_api_tls,pandaproxy_api_tls, andschema_registry_api_tlsto explicit nulls when no listener on that API serves TLS. The keys are now omitted. -
listeners.<api>.external.<listener-name>.nodePorthas no effect. The LoadBalancer Service now publishes the first entry ofadvertisedPorts, or the port of the listener ifadvertisedPortsis empty.