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.2.6 |
Pipeline resources gain rolling updates and RPC plugin support, StretchCluster brokers now advertise their configured external addresses, and scaling down several brokers at once now decommissions each one before the next. |
|
v26.2.5 |
NodePool brokers inherit an unset image from the Redpanda resource, Console and Pipeline resources connect to NodePool brokers, and the operator and the default Redpanda image no longer trust the compromised eMudhra certificate authorities (CVE-2026-111943). |
|
v26.2.4 |
A rolling restart no longer deletes the PersistentVolumeClaims of live brokers, |
|
v26.2.3 |
Rolling restarts wait for Schema Registry to catch up on each broker, the multicluster metrics endpoint is served over HTTPS by default, and the operator’s alerts and Grafana dashboard are scoped to one operator install. |
|
v26.2.2 |
Recovery for brokers that crashloop with a retired identity, a fix for CRD installation on Kubernetes versions that enforce CEL reserved-word escaping, and correct |
|
v26.2.1 |
Adds the beta |
v26.2.6 (2026-11-11)
Pipeline resources gain rolling updates and RPC plugin support, StretchCluster brokers now advertise their configured external addresses, and scaling down several brokers at once now decommissions each one before the next.
|
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.2.6 \
--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
-
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.Details
For example, add a manifest in
spec.configFileswith the plugin built into a customspec.image, or copy in a static binary withspec.extraInitContainers.
Improvements
-
The default Redpanda Connect image for
Pipelineresources is now 4.117.0. Pipeline resources that do not setspec.imagemove to it on upgrade. -
The default Redpanda Console image for
Consoleresources is now v3.14.0. Console resources that do not set an image move to it on upgrade.
Bug fixes
-
StretchCluster broker 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 to apply it, and atimeoutSecondsset through a RedpandaBrokerPoolpodTemplatestill overrides it. -
Upgrading the operator no longer restarts every broker just because the embedded Redpanda chart’s version changed. The upgrade to this release restarts brokers managed by
Redpandaresources once to drop thehelm.sh/chartlabel from their Pods. -
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. Previously, several broker Pods could be deleted at once with only the first decommissioned, so partitions with a majority of replicas on them lost quorum. -
Topic resources without
spec.partitionsorspec.replicationFactorno longer fail every reconcile after the topic is created. The operator now leaves the topic’s current partition count and replication factor alone when those fields are unset. -
StretchCluster brokers now advertise the same host as their LoadBalancer Service on external Kafka and HTTP Proxy listeners while
external.enabledis true, and each pool now uses its ownexternal.addresseslist. Pools that setexternal.domainorexternal.addressesadvertise the new address after the next broker restart, so create DNS records for those names before you upgrade. -
Pipelines with
userRefnow get theirRPK_SASL_*environment variables from the referenced User instead of the cluster’s bootstrap user. -
Resources that reference a cluster through
cluster.clusterRef, such asUser,Topic,Schema, andRole, no longer fail witherror fetching server root CA <namespace>/<cluster>-<cert>-root-certificate: server TLS certificate not foundwhen the cluster’s certificate setstls.certs.<cert>.issuerRef. ForissuerRefandsecretRefcertificates alike, the operator now trusts every certificate in the issued Secret’sca.crtwhencaEnabledis true, or itstls.crtotherwise, so a CA bundle or a full chain works. -
A StretchCluster’s
status.nodePoolsno longer keeps the entry of a removed node pool. An entry is removed only by a reconcile that observes every member cluster, so the pools of an unreachable member are kept. -
A StretchCluster reconcile that cannot fully read a member cluster now skips that member instead of acting on its partial state, which could change a StatefulSet’s replica count without decommissioning the removed brokers. In flat network mode, resource rendering now waits until every member’s pools are fetched, instead of deleting the member’s per-pod Endpoints and EndpointSlices and breaking DNS to its brokers.
Details
While any member is skipped or its broker pools are not listed, the operator no longer scales a pool down without decommissioning. The
ResourcesSyncedcondition names the members it waits for. Reads of a member’s Pods, ControllerRevisions, and StatefulSet selector now time out, so a member whose API server stops answering no longer stalls the reconcile. -
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, for Redpanda resources, the post-install Job now mount the trust stores so they can connect to the Admin API. Brokers with atrustStoreon one of these listeners restart once on upgrade.Details
If the listener’s certificate also has a CA (
caEnabled), these clients verify it with a bundle ofca.crtand the trust store. A newserver-ca-bundleinit container writes the bundle when the Pod starts, and the sidecar rewrites it whenca.crtor the trust store changes, so clients pick up the change without a restart. A broker keeps verifying with the trust store alone until it restarts on the new Pod template.
v26.2.5 (2026-10-23)
NodePool brokers inherit an unset image from the Redpanda resource, Console and Pipeline resources connect to NodePool brokers, and the operator and the default Redpanda image no longer trust the compromised eMudhra certificate authorities (CVE-2026-111943).
|
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.2.5 \
--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.
Improvements
-
StretchCluster lifecycle hooks now log a TIMEOUT line when
postStart.shorpreStop.shis killed at its timeout, matching the Helm chart. Previously, the hook was killed silently. -
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 StretchCluster brokers now setssecurityContext.runAsNonRoot: trueandsecurityContext.allowPrivilegeEscalation: false, matching the Redpanda Helm chart andRedpandaPods. StretchCluster brokers restart on upgrade. -
values.schema.jsonis now 3-5x smaller, so everyhelm template,helm install, andhelm upgradespends less time compiling it. Arrays nested inside a list or map of objects, such aspodTemplate.spec.containers[].args, now acceptnullas well as a list. -
The default Redpanda Connect image for
Pipelineresources is now 4.115.0. -
The default Redpanda image tag (
--redpanda-tag) is now v26.2.6, whose image no longer trusts the compromised eMudhra certificate authorities (CVE-2026-111943).
Bug fixes
-
The operator no longer sorts string-array cluster configuration values before applying them. Order-sensitive properties such as
kafka_mtls_principal_mapping_rules,sasl_kerberos_principal_mapping, andiceberg_default_catalog_namespacenow keep the order given in the Redpanda resource. -
The sidecar started by
--watch-usersnow retries a user sync when the broker’s Admin API is not yet listening or returns an error. Previously, SASL users from the users secret were sometimes not created until the secret changed or the Pod restarted. -
A
Consolethat references a Redpanda cluster throughclusterRefnow connects to the cluster’s NodePool brokers. With--enable-v2-nodepools, Console no longer crash-loops after a NodePool migration drains the cluster’s own StatefulSet tostatefulset.replicas: 0. -
A
Pipelinethat references a Redpanda cluster throughclusterRefnow connects to the cluster’s NodePool brokers. With--enable-v2-nodepools, a Pipeline no longer loses its seed brokers after a NodePool migration drains the cluster’s own StatefulSet tostatefulset.replicas: 0. -
NodePool brokers now inherit any unset
imagefield from the Redpanda resource instead of the operator’s default Redpanda image, which produced a mixed-version cluster when the Redpanda resource pinnedimage.tag. On upgrade, NodePools that leaveimageunset roll to the Redpanda resource’s image, so first setimage.tagto the version the NodePool runs today. -
Brokers managed by the Redpanda and StretchCluster resources are no longer left in maintenance mode after a rolling restart when their Admin API takes longer than the
postStarthook timeout to start. -
The operator is now built with Go 1.26.10, which rejects certificates chaining to the compromised eMudhra intermediate certificate authorities (CVE-2026-111943) and fixes several HTTP/2 denial-of-service vulnerabilities.
-
golang.org/x/netis updated to v0.60.0,golang.org/x/cryptoto v0.57.0, and OpenTelemetry to v1.46.0 (logs v0.22.0) to address reported vulnerabilities, including a busy-spin in the OpenTelemetry log batch processor (CVE-2026-81872).
v26.2.4 (2026-09-24)
A rolling restart no longer deletes the PersistentVolumeClaims of live brokers, podTemplate applies to every workload the operator chart renders, and the commonAnnotations value is renamed to connectAnnotations.
|
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.2.4 \
--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
-
podTemplatenow applies to every workload the chart renders: the operator Deployment, the CRD installation Job, and the post-upgrade migration Job. Both Jobs now inherit its default PodsecurityContext(runAsUser: 65532), which previously reached only the Deployment.Details
To override one workload, set
deployment.podTemplate,jobs.crd.podTemplate, orjobs.migration.podTemplate. Each one layers on top ofpodTemplate, which makes the containersecurityContextof the hook Jobs configurable. Pod templates are merged by name, so to override one container, give the name of that container in the override.
Improvements
-
Breaking change for Redpanda Connect pipelines, which are still in beta: the operator chart’s
commonAnnotationsvalue is renamed toconnectAnnotations, and the operator’s--common-annotationsflag to--connect-annotations. Rename the value before you upgrade, becausehelm upgradefails on the old name.
Bug fixes
-
Setting
post_install_job.enabled=falseno longer prevents cluster configuration from being applied. Environment variables injected throughpost_install_job.podTemplateno longer feed cluster configuration, so useconfig.extraClusterConfigurationorstorage.tiered.credentialsSecretRefinstead. -
In the multicluster operator, a persistently failing maintenance-mode, stale-disk-wipe, or decommission step no longer blocks a StretchCluster’s cluster configuration and license synchronization. Previously,
ConfigurationAppliedcould reportTrueindefinitely while spec changes were never applied. -
StretchCluster admin, Kafka, and Schema Registry clients no longer connect to broker Pods on a node that has gone NotReady. Previously, connection timeouts to those unreachable Pods stalled decommission and pool cleanup.
-
StretchCluster clients keep at least two admin hosts when endpoint filtering leaves a single broker, instead of failing every request against that one broker.
-
Deleting a Redpanda or StretchCluster no longer waits for the 3-minute periodic requeue before its finalizer is removed.
-
Objects rendered by the operator chart no longer carry
annotations: nullwhen no annotations are configured. Previously, Argo CD kept the ServiceMonitor and every other chart object permanently OutOfSync. -
The Console configuration rendered for a Redpanda resource no longer contains
kafka.sasl.enabled: trueandkafka.sasl.impersonateUser: trueunless the legacyconsole.consoleblock configures a login. Previously, Console 3.9 crash-looped on clusters without SASL. -
The StatefulSet decommissioner no longer deletes the PersistentVolumeClaims of live brokers during a rolling restart. On Redpanda (v2) clusters, the operator-wide decommissioner now deletes claims only when
--auto-delete-pvcsis set.Details
Previously, updating a StatefulSet could delete the claims of Pods that had not yet rolled. Those Pods came back onto empty volumes and rejoined the cluster as new brokers. The decommissioner started by
--additional-controllers=decommission(orall) also deleted claims by default. If you rely on it to remove the claims that a scale-down leaves behind, pass--auto-delete-pvcs.
v26.2.3 (2026-09-03)
Rolling restarts wait for Schema Registry to catch up on each broker, the multicluster metrics endpoint is served over HTTPS by default, and the operator’s alerts and Grafana dashboard are scoped to one operator install.
|
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.2.3 \
--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
-
The operator chart can add a label to operator metrics that identifies which Kubernetes cluster each series came from. Set
monitoring.clusterLabel.enabledtotrue(off by default) when metrics from more than one Kubernetes cluster land in the same Prometheus-compatible backend.Details
In multicluster mode, the label value defaults to
multicluster.name. Otherwise, setmonitoring.clusterLabel.value. -
Rolling restarts now wait for each broker’s Schema Registry store to catch up on
_schemasbefore rolling the next broker, so a cluster keeps a consistent Schema Registry endpoint during an upgrade. This applies to Cluster, Redpanda, and StretchCluster resources, and is skipped on clusters without a Schema Registry listener. To disable it, pass--wait-for-schema-registry-sync=false. -
The single-cluster operator supports
--leader-election-lease-duration,--leader-election-renew-deadline, and--leader-election-retry-periodfor tuning leader election. The existing defaults of 15s, 10s, and 2s are unchanged. -
Telemetry now reports
id_hashfor clusters licensed through their custom resource, not only for operators given their own license file. A newclusterLicensesfield carries the distinct license checksums found across managed clusters and the count of validly licensed clusters.
Bug fixes
-
The sidecar no longer writes malformed users-file lines, which can contain passwords, to its log. When the sidecar manages the
superuserscluster property, it now sets the property once per sync pass with the users from every users file, instead of once per file. -
The
multiclustercommand now serves its metrics endpoint over HTTPS by default, so the operator chart’s ServiceMonitor can scrape a multicluster deployment. If you overrode the ServiceMonitor toscheme: http, remove that override, or pass--metrics-secure=falseto keep the plain-HTTP endpoint. -
An unreadable broker list no longer stops the whole reconcile pass. Previously, a transient read failure against a broker whose Pod was already gone also stopped decommissioning and cluster configuration sync, so that broker was never removed.
-
The StretchCluster admin, Kafka, and Schema Registry clients no longer try brokers whose Pod cannot be reached, such as a terminating or finished Pod. If no Pod looks reachable, the clients use the full declared broker list as before.
-
The
monitoring.rulesEnabledalerts and the shipped Grafana dashboard now apply only to this operator install, byjobandnamespace. Previously, the alerts could fire for other controllers in the same Prometheus, such as Karpenter, Flux, cert-manager, or a second operator install. The dashboard gains Namespace and Job pickers, plus one for themonitoring.clusterLabellabel. -
The
OperatorReconcileRunawayandOperatorWorkerPoolSaturatedalerts no longer fire during healthy interval reconciliation. A newOperatorReconcileChurnalert tracks non-interval work, andOperatorWorkerPoolSaturatednow measures sustained workqueue delay instead of worker utilization. -
User, Role, and Group resources now reconcile on clusters with
listeners.schemaRegistry.enabled=false. Previously, a disabled Schema Registry listener blocked all ACL syncs. -
The multicluster operator now reports telemetry. Previously, it dropped every report.
v26.2.2 (2026-08-17)
Recovery for brokers that crashloop with a retired identity, a fix for CRD installation on Kubernetes versions that enforce CEL reserved-word escaping, and correct cluster.redpanda.com/nodepool labels on every node pool.
|
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.2.2 \
--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.
Bug fixes
-
The operator now recovers a broker that crashloops because it starts with a retired identity that the controller refuses (
bad_rejoin), on single-cluster and StretchCluster resources, with or without persistent storage. The operator needs a new permission for this: get onpods/log, which the generated roles include.Details
The operator clears a leaked maintenance-mode flag on a dead broker whose address a live successor already owns. This does not depend on
--wipe-stale-disk-after. The operator 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, so that the broker restarts with a new identity. 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. Zero or a negative value disables it. The StretchCluster operator keeps its existing default of5m. -
On StretchCluster resources, the preStop lifecycle hook no longer stalls Pod termination or stops a broker in the middle of a drain. The hook skips the drain for a broker that is no longer a cluster member, and every admin API call in the hook has a timeout.
-
CRD installation no longer fails on Kubernetes versions that enforce CEL reserved-word escaping (observed on 1.31). Previously, a fresh install of operator v26.2.1 with
crds.enabled=truecould not complete on those versions. -
Each node pool’s Pods now carry their own
cluster.redpanda.com/nodepoollabel. Previously, every pool after the first got the first pool’s label. -
The operator chart’s
ServiceMonitorand the StretchCluster per-poolServiceMonitorresources now use lowercasescheme: httporscheme: https. Olderprometheus-operatorCRDs reject the uppercase values. -
The post-upgrade migration job no longer fails the whole upgrade when its ServiceAccount lacks permissions for optional resource types, such as Gateway API
tlsroutesorhttprouteson clusters that manage RBAC manually (rbac.create=false). The job logs a warning, skips the resource, and checks it again on the next upgrade. -
Operator telemetry now works in the official release images. In earlier images, including v26.2.1, the telemetry client was disabled.
v26.2.1 (2026-07-28)
Adds the beta Pipeline CRD for Redpanda Connect, per-broker probes that gate rolling restarts, and ShadowLink role and schema replication that is on by default, along with many StretchCluster and PVCUnbinder fixes.
|
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.2.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
-
Console can be exposed through Gateway API controllers as an alternative to Ingress. The Console CRD supports HTTPRoute.
-
The operator uses the per-broker pre-restart and post-restart probes in Redpanda 25.1+ to gate rolling restarts of Redpanda and StretchCluster resources: it restarts a broker only when the probe reports no risk of data loss or unavailability (a topic with a replication factor of 1 going offline is accepted), and waits for that broker to finish recovery before it restarts the next one. Clusters older than 25.1 keep the cluster-wide health check, and
--post-restart-caught-up-percent(default 100) sets how much recovery is required. -
clusterRefaccepts an optionalnamespacefield on ShadowLink, Topic, User, Role, Schema, and Group resources, so a resource can reference a cluster in another namespace. A ShadowLink between two namespaces on the same Kubernetes cluster is intended mainly for development and test clusters. -
The operator can report optional anonymous telemetry about cluster shape, such as cluster and broker counts, Redpanda versions in use, and feature adoption, and licensed clusters also report the enterprise license checksum. Disable it with the
telemetry.enabledchart value or--disable-telemetry. Telemetry does not run in the published v26.2.1 images. It works from v26.2.2. -
The operator Helm chart has a top-level
priorityClassNamevalue. Set it to a higher-priority PriorityClass so the operator Pod is less likely to be preempted when the cluster is under resource pressure. -
The
rpk-k8sCLI is published as a managedrpkplugin with each operator release. Run it withrpk k8s, andrpkdownloads, verifies, and caches it on first use. -
A Broker custom resource and controller manage the Pod and PVC lifecycle of individual brokers. This is experimental and runs only when you set
--enable-broker. -
Kubernetes versions 1.33.x through 1.36.x are supported.
-
The operator automatically clears maintenance mode on a broker that is stuck in it, for example because its Pod cannot reschedule from a cordoned or lost node, which unblocks auto-decommission. This applies to Redpanda and StretchCluster resources when the cluster reports the broker as not alive and the Pod is not-Ready for 30m by default, and
--clear-maintenance-mode-afterchanges the threshold. -
For a StretchCluster, the operator can recover a broker that crash-loops after a region outage because it boots from a stale disk: it deletes the Pod and its PVC so that the broker reschedules onto a fresh disk. This runs only when the broker’s on-disk identity collides with the cluster’s view, the cluster is healthy, and the Pod is not-Ready for 5m by default. Set
--wipe-stale-disk-afterto change the threshold, or to a negative value to disable it. -
ShadowLink resources expose
spec.clientOptionsto tune the Kafka client that the shadow cluster uses to fetch from the source cluster. Unset fields keep the broker default, so existing ShadowLinks are unaffected. -
ShadowLink replicates RBAC roles and schemas from the source cluster by default, controlled by
spec.roleSyncOptionsandspec.schemaRegistrySyncOptions. Existing ShadowLinks start replicating all roles and the source cluster’s schemas topic on the first reconcile after upgrade.Details
Replicated roles may include privileged or superuser roles. To keep the previous behavior, set
spec.roleSyncOptions.enabled: falseandspec.schemaRegistrySyncOptions.enabled: falseon existing ShadowLinks before you upgrade the operator. Schemas can also be replicated from an external schema registry, for example a Confluent Schema Registry, withspec.schemaRegistrySyncOptions.shadowSchemaRegistryAPI. -
The
PipelineCRD and Connect controller (beta) run Redpanda Connect pipelines declaratively, with support forkubectl scaleand HorizontalPodAutoscaler, and roll pipeline Pods when the configuration or a referenced Secret or ConfigMap changes. This is an enterprise feature and is disabled by default.Details
To opt in, set
connectController.enabled: truein the operator Helm chart values, or pass--enable-connect. Configure the enterprise license for the operator withenterprise.licenseSecretRefin the chart values.
Improvements
-
--additional-controllers=decommissionnow runs the NodePool-awareStatefulSetDecommissionerforRedpandaclusters, which is correct for clusters split across multiple NodePools. Operators that already passdecommissionorallswitch to it on upgrade with no configuration change. -
The Console controller now honors the
namespacefield ofclusterSource.clusterRef. Previously, it always resolved the cluster in the Console’s own namespace, so a Console could fail to find its cluster or bind to a same-named cluster in the wrong namespace. -
Sync intervals for the Topic, User, Group, Schema, Role, and ShadowLink controllers are now configurable with flags such as
--topic-sync-intervalor with thecontrollers.<resource>.intervalHelm chart values. TheTopicCRD no longer sets a defaultintervalof3s, so new Topics use the operator default of 30s, but existing Topics keep reconciling every 3s until you clear the stored value.Details
Topic defaults to 30s. User, Group, Schema, Role, and ShadowLink default to 5m. A
spec.intervalset on aTopictakes precedence over the operator default. To make an existingTopicadopt the operator default, remove its stored value:kubectl patch topic <name> --type=json -p='[{"op":"remove","path":"/spec/interval"}]' -
The SASL mechanism fields on the Redpanda and StretchCluster CRDs now accept only
SCRAM-SHA-256orSCRAM-SHA-512, so an invalid value is rejected at apply time. Existing objects are not re-checked on upgrade, but the next update of an object with any other value, includingmechanism: "", is rejected, so correct the value or omit the field.
Bug fixes
-
A Redpanda resource that renders TLSRoute objects through the chart’s Gateway API support no longer causes a
no kind "TLSRouteList" / "ListOptions" is registered for version "gateway.networking.k8s.io/v1"error on every reconcile. -
A single reconcile no longer deletes more than one broker Pod during a rolling restart, for Redpanda and StretchCluster resources. Previously, a transient Admin API error or an address-format mismatch could make the operator treat every Pod as an orphan and delete them all at once.
-
The broker decommissioner (
--additional-controllers=decommission) now builds the correct broker hostname whenfullnameOverrideis set. Previously, its health check failed withno such hostand decommission and PVC cleanup never completed. -
The broker decommissioner now handles clusters split across multiple NodePools: it compares the total broker count against the sum of every pool’s desired replicas and acts only on the Pods of each pool’s own StatefulSet.
-
The PVCUnbinder no longer acts on several Pending broker Pods at once during a cluster-wide disruption, which could delete every broker’s PVCs in parallel. It now defers when stuck Pods span more than one node, when another unbind is in progress, or when the parent resource has the
operator.redpanda.com/pause-pvc-unbinder=trueannotation.Details
A new
--broker-pod-node-unavailable-tolerationflag adds long NotReady and Unreachable tolerations to broker Pods, so brief node unreachability does not lead to an unbind.--allow-pv-rebindingis deprecated because the new checks make it unnecessary and unsafe. -
The Topic controller no longer issues a no-op
IncrementalAlterConfigsrequest on every reconcile. It writes only the configuration keys that differ from the live broker configuration. -
The Topic, User, Group, Schema, Role, and ShadowLink controllers no longer reconcile every resource on each status-only update of the referenced cluster, so configured sync intervals such as the Topic
spec.intervaltake effect. -
clusterSpec.statefulset.extraVolumeMounts,livenessProbe, andstartupProbenow apply to theredpandacontainer. Previously, they applied only to thesidecarcontainer. -
The
rpkconfiguration inside broker Pods no longer goes stale after brokers join or leave the cluster, for bothClusterandRedpandaresources. Brokers restart once on upgrade, and if you pin--configurator-tagorsideCars.image.tagto an older operator release, you must bump the pin to this release or later. -
clusterSpec.statefulsetoverrides such as probes andextraVolumeMountsare no longer dropped whenpodTemplate.spec.containersorpodTemplate.spec.initContainerscontains duplicate entries with the same name. -
Flags set in
additionalCmdFlagsnow override the defaults that the chart sets, such as--enable-console. Previously, they were silently dropped. -
Deleting a User no longer gets stuck on clusters without an enterprise license. Previously, Schema Registry ACL cleanup failed with "Invalid license: not present" and the finalizer was never removed.
-
A StretchCluster peer whose
StretchClusterresource has been removed is no longer reported asSpecSynced=ClusterUnreachable, and no longer blocks the cluster from reachingStable. -
A
StretchClusterwith SASL authentication disabled now sets theBootstrapUserSyncedcondition toTrue. Previously, the condition stayedUnknown, which kept an otherwise healthy cluster from reachingStable. -
Operator logs for
StretchClusterrolling restarts and StatefulSet changes now include the cluster name instead of a blank identifier. -
The Redpanda and
StretchClusterreconcilers no longer stall recovery when no broker is Ready, for example during a full-region outage. The operator now still clears stuck maintenance mode, decommissions brokers, and, for a StretchCluster, wipes stale disks. -
A StretchCluster with
rackAwareness.enabled: truecan now deploy from a default chart install. On multicluster installs, the operator chart now grants the operator ServiceAccountnodes: get/list/watch. -
Setting
tls.enabled: falseon a RedpandaBrokerPool now also disables TLS on the default external listeners, so brokers no longer crash-loop with "Could not read trust file". Also, aclusterRef.groupvalue that contains a version suffix, such ascluster.redpanda.com/v1alpha2, is now rejected by CRD validation instead of silently never binding. -
The User CRD now accepts
spec.authentication.password.valueon its own, as documented. Previously,password.valueFromwas always required. -
The PVCUnbinder no longer deadlocks a cluster that uses WaitForFirstConsumer volume binding when a Pending Pod holds a local volume on a node that is unavailable or already occupied. Previously, a fresh cluster in this state never bootstrapped.
Details
The unbinder’s ClusterRole now also grants nodes list and storageclasses get. If RBAC that you manage lacks them, the unbinder keeps deferring. To turn off only this behavior, set
--disable-pvc-rebinding-gate-exemption, orstatefulset.sideCars.pvcUnbinder.disableStuckClaimExemptionin the redpanda chart. When two brokers are affected on two nodes, you must still delete the PVC manually. -
The operator now clears maintenance mode on a dead broker ID that was replaced by a live broker at the same address, which happens when a Pod loses its data directory and rejoins the cluster. This requires a stable advertised DNS address, so brokers that advertise bare Pod IPs are not matched.
-
Applying the same StretchCluster manifest to every member cluster at once, for example with a GitOps controller, no longer stores different bootstrap-user passwords across clusters. Previously, this permanently halted reconciliation with
Cluster has no desired brokers. -
StretchCluster now honors
spec.auth.sasl.bootstrapUser.secretKeyRefand replicates the password to every member cluster. Previously, the field was ignored and the operator always used its own<name>-bootstrap-userSecret. -
A StretchCluster whose
bootstrapUser.secretKeyRefpoints at a Secret with no data under the referenced key now reports an error on theBootstrapUserSyncedcondition. Previously, the operator generated a new password and wrote it to only some member clusters. -
Adding a
bootstrapUser.secretKeyRefto a StretchCluster that was bootstrapped with the operator-managed<name>-bootstrap-userSecret no longer breaks operator authentication. The operator keeps the original password and copies it to the referenced location, and reports an error if that location already holds a different password. -
SASL authentication now works on StretchClusters that use the default SCRAM mechanism, so User resources and ACL sync no longer fail with SASL_AUTHENTICATION_FAILED. Changing
auth.sasl.mechanismon a cluster that is already bootstrapped still causes the same failure. -
StretchCluster lifecycle hooks now clear maintenance mode left behind by a previous incarnation of the Pod that re-registered under a different node ID.
-
The StretchCluster controller no longer renders broker StatefulSets and ConfigMaps when it cannot observe a peer cluster’s broker pools. Previously, a broker in a newly added RedpandaBrokerPool could start with only itself in
seed_serversand form a separate cluster. -
Changing
spec.authentication.typeon an existingUsernow rewrites the user’s SCRAM credential under the new mechanism. Previously, nothing was written and theUserstill reportedSynced=True.Details
For a
Userwhosetypewas edited but never took effect, the first reconcile after upgrade applies the change, and the credential under the previous mechanism stops working. Migrate clients first. Deleting aUsernow removes the mechanisms that the cluster actually holds. On brokers too old to support the Kafka SCRAM describe API, atypechange is still not detected.
Deprecations
-
The
--allow-pv-rebindingflag is deprecated because the new PVCUnbinder checks make it unnecessary and unsafe. -
The old broker
DecommissionReconcileris deprecated and will be removed in a future release. It is available only with--additional-controllers=legacy-decommission, whichalldoes not include.