Redpanda Operator Release Notes
This page lists the changes in each Redpanda Operator 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 operator release changes the sidecar image that runs in the broker Pods, so upgrading the operator restarts the brokers of Redpanda and StretchCluster resources. The Upgrade notes column says whether a release has anything else to know before you upgrade.
For a summary of the major features in this release line, see What’s New in the Redpanda Operator. To check which versions of Redpanda, Kubernetes, and Helm each release supports, see Kubernetes Compatibility.
| Version | Highlights | Upgrade notes |
|---|---|---|
v26.3.1 |
RedpandaBrokerPool replaces NodePool, Redpanda Connect support is now GA, and Broker resources (beta) let a cluster move its brokers from StatefulSets to per-broker Broker resources with no restarts. |
v26.3.1 (2026-11-20)
RedpandaBrokerPool replaces NodePool, Redpanda Connect support is now GA, and Broker resources (beta) let a cluster move its brokers from StatefulSets to per-broker Broker resources with no restarts.
|
Before you upgrade
|
helm repo add redpanda https://charts.redpanda.com
helm repo update
helm upgrade --install redpanda-controller redpanda/operator \
--namespace <namespace> \
--create-namespace \
--version 26.3.1 \
--set crds.enabled=true \
--values <values-file>
Replace <values-file> with the file that holds your overrides. For the full procedure, see Upgrade the Redpanda Operator.
New features
-
RedpandaBrokerPool replaces NodePool for defining the pools of a Redpanda cluster, and requires an enterprise license (
enterprise.licenseSecretRefin the operator chart). Without one, the operator makes no changes to the cluster’s resources or pools.Details
To move a pool from a NodePool without rolling its brokers, install the experimental NodePool CRD (
crds.experimental: true), run the operator with--enable-v2-nodepools, create a RedpandaBrokerPool with the same name,clusterRef, and spec, then annotate the NodePool withoperator.redpanda.com/migrate-to-broker-pool: "true"or delete it. Do not downgrade the operator below this version once a RedpandaBrokerPool owns a pool that no NodePool defines. -
Broker resources (beta): annotating a Redpanda resource with
operator.redpanda.com/use-broker-crmoves its broker Pods from StatefulSets to per-broker Broker resources in place, with no restarts, and removing the annotation rolls back the same way. Migration and rollback progress shows in theBrokerMigrationcondition.Details
The operator must run with
--enable-broker, and the experimental Broker CRD must be installed (crds.experimental: truein the operator chart). Configuration changes made while the cluster uses Broker resources roll through the normal health-gated update flow, one broker at a time. -
With Broker resources, a detect-disk-lost init container refuses to start Redpanda when a broker’s data volume is provably empty, so a wiped or replaced disk never re-registers the broker under a new node ID. The Broker is marked
DiskLost, a replacement Broker takes its slot, and a DiskLostRemediated Warning event records the recovery. -
When a broker refuses to start on a new major version because the cluster uses enterprise features without a license, Redpanda and StretchCluster resources now report it:
LicenseValidis False with reasonUpgradeRefused,status.license.violationis true, and aBrokerStartupRefusedWarning event is emitted. -
kubectl get -o widefor Redpanda and StretchCluster resources now shows the license type and expiration, whether enterprise features are in use without a valid license, and the enterprise features in use. -
Pipeline resources have a new
spec.updateStrategyfield.Rollingstarts a new Pod and waits for it to be ready before stopping an old one, so inputs that cannot replay, such as core NATS, no longer drop messages during restarts;Recreatestays the default.Details
With
Rolling, old and new Pods briefly overlap and may process some messages twice. KeepRecreatefor inputs that need exclusive ownership, such as CDC replication slots. -
Pipeline resources have a new
spec.rpcPluginsfield that lists Redpanda Connect dynamic (RPC) plugin manifest paths or globs. The manifests and plugin executables must already be in the Pod. -
The Redpanda CRD gains
spec.clusterSpec.service.internal.perPort. Withenabled: true, the operator creates one Service per API and publishes a broker on each only while that API passes its health check, so clients avoid brokers that are restarting or, for Schema Registry, still catching up. -
The operator can manage a Service’s EndpointSlices itself, so a broker leaves a Kafka port while that listener refuses connections, and leaves the Schema Registry ports while its registry is still catching up. Opt in by annotating a Cluster or Redpanda resource with
operator.redpanda.com/enable-endpoint-steering=true. StretchClusters are not covered. -
Rolling restarts now wait for each broker’s Schema Registry to catch up before rolling the next broker. The check is skipped on clusters without a Schema Registry listener, and
--wait-for-schema-registry-sync=falsedisables it. -
The operator chart can add a scrape-time label that identifies which Kubernetes cluster a metrics series came from, through
monitoring.clusterLabel. It is off by default. -
podTemplatenow applies to every workload the operator chart renders, including the CRD installation Job and the post-upgrade migration Job. Newdeployment.podTemplate,jobs.crd.podTemplate, andjobs.migration.podTemplatevalues override each workload, and both Jobs now inherit the default podsecurityContext(runAsUser: 65532). -
The single-cluster operator supports
--leader-election-lease-duration,--leader-election-renew-deadline, and--leader-election-retry-periodfor tuning leader election. The defaults are unchanged. -
A new Prometheus gauge,
redpanda_broker_phase{namespace, kind, name, phase}, counts the Broker resources of each cluster in eachstatus.phase. -
The StretchCluster controller watches its rendered resources in every member cluster, so drift in an owned resource triggers reconciliation immediately.
-
rpk k8sreports each command’s flags and usage line to rpk, so shell completion lists their flags andrpk --print-treeincludes them. -
Anonymous operator telemetry reports the use of Broker resources, and
id_hashfor clusters licensed through their resource, not only through the operator’s own license file. -
The CRD reference documents every Console CRD field and the
Brokerresource, sokubectl explaindescribes them.
Improvements
-
Redpanda Connect support in the operator is now GA, including the
PipelineCRD and the Connect controller. The controller stays opt-in (--enable-connect/connectController.enabled) and requires an enterprise license with the Connect product. -
The configurator and fs-validator script volumes on
RedpandaandStretchClusterPods are now namedconfiguratorandfs-validator, without the<fullname>-prefix, which keeps the configurator volume name within the Kubernetes 63-character limit for releases whose full name is 51 characters or longer. Brokers restart on upgrade, and apodTemplateoverride keyed on an old volume name must be re-keyed to the new name. -
The
configuratorinit container of StretchClusters now carriessecurityContext.runAsNonRoot: trueandsecurityContext.allowPrivilegeEscalation: false, matching the chart andRedpandaPods. StretchCluster brokers restart on upgrade. -
The operator chart’s
commonAnnotationsvalue is renamed toconnectAnnotations, and the--common-annotationsflag to--connect-annotations. Rename it before upgrading: the chart’s values schema rejects unknown keys, so the old name failshelm upgrade. -
An unresolvable external secret referenced from cluster config now names the affected property, and the Redpanda resource’s
ConfigurationAppliedcondition and a Warning event carry the message. -
StretchCluster lifecycle hooks now log an explicit TIMEOUT line when
postStart.shorpreStop.shis killed at its timeout. -
StretchCluster sidecar and rack-awareness roles no longer grant permissions they never used. The operator owns these objects, so they narrow on upgrade with no action needed.
-
StretchCluster LoadBalancer Services now also carry a correctly spelled
redpanda.com/type: loadbalancerlabel. The misspelledrepdanda.com/typelabel is still set for existing selectors. -
values.schema.jsonis now 3-5x smaller, which reduces the time everyhelm template,helm install, andhelm upgradespends compiling it. The schema accepts the same values, except that arrays nested inside a list or map of objects now acceptnullas well as a list. -
The operator uses less CPU and memory by parsing the Redpanda chart’s default values once and caching the merged chart values for each distinct cluster spec.
-
With
--leader-elect, theruncommand validates the leader election flags at startup and exits with an error that names the conflicting flags. -
The default Redpanda Connect image for
Pipelineresources is now 4.119.0, the default Redpanda Console image forConsoleresources is now v3.15.0, and the default Redpanda image tag (--redpanda-tag) is now v26.3.1.
Bug fixes
-
Operator upgrades now reach broker Pods. Before, the StatefulSet kept its old Pod template until the Redpanda resource or a NodePool changed. The first upgrade to this release rolls brokers once if their template changed since it was last applied.
Details
With
image,statefulset.sideCars.imageandstatefulset.initContainerImagepinned andlogging.usageStats.enabled: false, brokers roll only when a release changes the broker Pod spec. -
Upgrading the operator no longer rolls every broker just because the embedded Redpanda chart’s version changed. The upgrade to this release rolls brokers once to drop the
helm.sh/chartlabel. -
A broker Pod that cannot start, for example one crash-looping after an upgrade or one whose image cannot be pulled, can now be fixed by changing the cluster resource. The operator replaces such a Pod once its Pod template changes, one Pod at a time, and never one whose broker other brokers still see running.
-
The operator recovers brokers wedged by a leader-restart ghost or a decommissioned broker’s bad_rejoin crashloop, on single-cluster and StretchCluster resources.
Details
The operator clears a leaked maintenance-mode flag on a dead broker whose address a live successor already owns. It can also delete the data directory PersistentVolumeClaim, if there is one, and the Pod of a broker whose on-disk identity collides with the cluster’s membership and that stays not ready past a threshold. It does this only when the cluster is healthy and no nodes are down. On the single-cluster operator, this deletion is disabled by default. To enable it, set
--wipe-stale-disk-afterto a positive duration. -
The StatefulSet decommissioner no longer deletes the PersistentVolumeClaims of live brokers during a rolling restart. On Redpanda clusters, the operator-wide decommissioner deletes claims only when
--auto-delete-pvcsis set. -
When a
RedpandaorStretchClusterStatefulSet scales down by more than one broker in a single change, the operator now waits for each removed Pod to be fully gone before it decommissions the next broker. -
Brokers are no longer left in maintenance mode after a rolling restart when they take longer than the
postStarthook timeout to start their Admin API. -
V1
Clusterrolling restarts no longer delete a Pod undrained when Redpanda refuses to enable maintenance mode, and resume with the broker already in maintenance mode when the StatefulSet changes mid-drain. -
Changing how a cluster’s internal listeners serve, such as enabling TLS or turning SASL on, no longer cuts the operator off from brokers it has yet to restart. TLS on the RPC listener still can’t be changed safely on a running cluster.
Details
A cluster already stuck on such a change when the operator is upgraded stays stuck: revert the change, wait for the cluster to settle, then apply it again. A
Redpandaresource’s RPC listener followstls.enabledunlesslisteners.rpc.tls.enabledis set, so set it to the listener’s current value before turning TLS on or off. -
Clients in Redpanda and StretchCluster broker Pods now verify internal Admin API, Kafka API, and Schema Registry listeners that have a
trustStore, and the sidecar and the post-install Job mount the trust stores. Brokers with atrustStoreon one of these listeners restart once on upgrade. -
The StretchCluster preStop lifecycle hook no longer stalls Pod termination or sends SIGTERM to a broker that is still draining, and bounds its Admin API calls.
-
StretchCluster startup and liveness probes now set
timeoutSeconds: 5, so Admin API responses slower than 1s no longer restart a healthy broker. StretchCluster brokers restart once on upgrade. -
StretchCluster clients no longer dial broker Pods that cannot be reached, including Pods on a node that has gone NotReady, and keep at least two admin hosts.
-
A StretchCluster reconcile that cannot fully read a member cluster now skips that member instead of acting on its partial state, and a persistently failing maintenance-mode, stale-disk-wipe, or decommission step no longer blocks cluster-config and license synchronization.
-
StretchCluster brokers now advertise their external address on external Kafka and HTTP Proxy listeners, and each pool uses its own
external.addresseslist. Pools that setexternal.domainorexternal.addressesadvertise the new address after the next broker restart. -
A StretchCluster listener with
tls.enabled: truein a pool that disables TLS now gets its certificate. Before, the broker crashlooped. -
StretchCluster LoadBalancer Services now publish the first advertised port of each external listener. Before, they published the listener port, but clients connect to the advertised port.
-
StretchCluster
ClusterRoleandClusterRoleBindingnames are no longer truncated to 63 characters, so pools no longer overwrite each other’s rules. -
A retired node pool is now removed from
status.nodePoolson Redpanda and StretchCluster resources instead of lingering with its last replica counts. -
NodePool brokers now inherit an unset
imagefield from the Redpanda resource instead of the operator’s default image. NodePools that leaveimageunset roll to the Redpanda resource’s image on upgrade. -
A
ConsoleorPipelinethat references a cluster throughclusterRefnow connects to the cluster’s NodePool brokers when the operator runs with--enable-v2-nodepools. -
Redpanda clusters whose certificates set
caEnabled: falseare now reachable over TLS from the operator, Console, and Pipelines. -
Resources that reference a cluster through
cluster.clusterRefno longer fail to fetch the server root CA when the cluster’s certificate setstls.certs.<cert>.issuerRef, and a CA bundle or a full chain works. -
User, Role, and Group resources now reconcile on clusters with
listeners.schemaRegistry.enabled=false. -
SASL users from the users Secret are now created when the broker’s Admin API is not yet listening at the first sync. The sidecar retries with backoff.
-
The operator no longer sorts string-array cluster configuration values, so order-sensitive properties such as
kafka_mtls_principal_mapping_ruleskeep the order given in the Redpanda resource. -
When a broker rejects a cluster configuration write, the
ConfigurationAppliedcondition and a Warning event carry the broker’s per-property reason instead of a bareBad Request. -
A ShadowLink whose link has been failed over no longer reports
Synced=Falseand re-sends the refused update on every reconcile. The operator stops updating a link once failover starts and reports its state instatus.state. -
Setting
post_install_job.enabled=falseno longer prevents cluster configuration from being applied. Useconfig.extraClusterConfigurationorstorage.tiered.credentialsSecretRefinstead of environment injected throughpost_install_job.podTemplate. -
Topic resources without
spec.partitionsorspec.replicationFactorno longer fail every reconcile after the topic is created. -
An interrupted
RedpandaRolerename no longer orphans the old role. The newstatus.pendingEffectiveRoleNamefield lets the next reconciliation retry the rename. -
Pipelines with
userRefnow get theirRPK_SASL_*environment variables from the referenced User instead of the cluster’s bootstrap user. -
The Console configuration rendered for a Redpanda resource no longer enables SASL impersonation unless the legacy
console.consoleblock configured a login, so clusters without SASL no longer get a crash-looping Console. -
With Broker resources, the PodDisruptionBudget now allows disruptions, so
kubectl drainno longer hangs on nodes that run a broker. Broker resources also fix restarts after the first restart-requiring configuration change, and status for node pools scaled to zero. -
The V1 Cluster controller no longer removes the cluster_id cluster configuration property on every configuration reassertion.
-
Deleting a Redpanda or StretchCluster no longer waits for the 3-minute periodic requeue before its finalizer is removed.
-
CRD installation no longer fails on Kubernetes versions that enforce CEL reserved-word escaping.
-
The multicluster operator now serves metrics over HTTPS by default, so the operator chart’s ServiceMonitor can scrape it, and it now reports telemetry.
-
The operator chart’s ServiceMonitors emit a lowercase
scheme, so olderprometheus-operatorCRDs accept them. -
The
monitoring.rulesEnabledPrometheusRule and the Grafana dashboard now scope every expression to this operator install, so alerts no longer fire for other controllers or other operator installs. False-positiveOperatorReconcileRunawayandOperatorWorkerPoolSaturatedalerts no longer fire during healthy interval reconciliation, and a newOperatorReconcileChurnalert tracks non-interval work. -
Objects rendered by the operator chart no longer carry
annotations: null, so ArgoCD no longer reports them as permanently OutOfSync. -
The post-upgrade migration Job no longer fails the upgrade when its ServiceAccount lacks permissions for optional resource types, and the field-manager migration now fully releases a resource whose only manager is a legacy one.
-
Nodepools after the first no longer inherit the first nodepool’s cluster.redpanda.com/nodepool label.
-
Official release images now embed the telemetry signing key, enabling operator telemetry.
-
The sidecar no longer writes malformed users-file lines, which can contain passwords, to its log.
-
The
resources.memory.enable_memory_lockingdescription no longer says to set it totruefor production, and thecloud_storage_*field descriptions link to the Object Storage Properties page.
Deprecations
-
NodePool is deprecated in favor of RedpandaBrokerPool and will be removed in a future release.
-
The misspelled
repdanda.com/typelabel on stretch-cluster LoadBalancer Services will be removed in the next major release.
Removed
-
nodePorton Redpanda external listeners has no effect. UseadvertisedPortsinstead. -
The operator no longer migrates
spec.clusterSpec.consolein a Redpanda resource to a Console resource, and ignores the field. To deploy Redpanda Console, create a Console resource. -
The deprecated
legacy-decommissioncontroller is removed. Use--additional-controllers=decommission, whichallalready selects.