# What’s New in the Redpanda Operator

> For the complete documentation index, see [llms.txt](https://docs.redpanda.com/llms.txt). Component-specific: [streaming-full.txt](https://docs.redpanda.com/streaming-full.txt)

---
title: What’s New in the Redpanda Operator
latest-redpanda-tag: v25.1.1
latest-console-tag: v3.7.3
latest-operator-version: v26.1.4
# EOL = End-of-Life (support lifecycle status)
page-is-nearing-eol: "false"
page-is-past-eol: "true"
page-eol-date: April 7, 2026
latest-connect-version: 4.93.0
docname: release-notes/operator
page-component-name: streaming
page-version: "25.1"
page-component-version: "25.1"
page-component-title: Streaming
page-relative-src-path: release-notes/operator.adoc
page-edit-url: https://github.com/redpanda-data/docs/edit/v/25.1/modules/get-started/pages/release-notes/operator.adoc
description: Summary of new features and updates in the Redpanda Operator.
page-git-created-date: "2025-04-07"
page-git-modified-date: "2026-05-26"
support-status: past end-of-life
---

<!-- Source: https://docs.redpanda.com/streaming/25.1/get-started/release-notes/operator.md -->

This topic includes new content and significant changes in the Redpanda Operator. For a complete list of all updates, see the [Redpanda Operator changelog](https://github.com/redpanda-data/redpanda-operator/blob/v26.1.4/operator/CHANGELOG.md).

See also:

-   [What’s New in Redpanda](https://docs.redpanda.com/streaming/25.1/get-started/release-notes/redpanda/)

-   [Kubernetes Compatibility](https://docs.redpanda.com/streaming/25.1/upgrade/k-compatibility/)

-   [Upgrade Redpanda in Kubernetes](https://docs.redpanda.com/streaming/25.1/upgrade/k-rolling-upgrade/)


## [](#redpanda-operator-v25-1-1-beta1)Redpanda Operator v25.1.1-beta1

[Changelog](https://github.com/redpanda-data/redpanda-operator/blob/release/v25.1.x/operator/CHANGELOG.md).

See also: [Try the 25.1 Beta of the Redpanda Operator](https://docs.redpanda.com/streaming/25.1/deploy/deployment-option/self-hosted/kubernetes/k-25.1-beta/)

### [](#multiple-operator-instances-deprecated)Multiple Operator instances (deprecated)

Support for deploying multiple instances of the Redpanda Operator in a single Kubernetes cluster is **deprecated** starting in Redpanda Operator v25.1.x. This feature will be removed in v25.2.x. For more information, see [Deploy multiple Redpanda clusters](https://docs.redpanda.com/streaming/25.1/deploy/deployment-option/self-hosted/kubernetes/k-production-deployment/#deploy-multiple-redpanda-clusters).

If you currently run multiple Operator instances, plan to migrate to a single Operator instance per cluster before upgrading to v25.2.x.

### [](#flux-removed)Flux removed

This release completely removes Flux and its CRDs. The Redpanda Operator now manages all resources. The `chartRef.useFlux` configuration is still available for backwards compatibility but MUST be set to `false`.

### [](#schema-validation)Schema validation

The Redpanda custom resource definition (CRD) now includes stricter schema validation to ensure configurations conform to expected standards. With this new schema validation enabled, you must ensure your Redpanda CRD configurations include valid fields.

For example, given the values:

```yaml
statefulset:
  replicas: "Not a number"
  liables:
    there-is: a-typo-in-this-field
```

In previous versions, you’d get an error about `statefulset.replicas` needing to be a number but no error about `liables` being an invalid field. In v25.1.x, you’ll get an error about `statefulset.replicas` needing to be a number and an error that `liables` isn’t an allowed field.

### [](#removed-fields)Removed fields

Deprecated fields have been removed from the CRD. Before upgrading, review your configurations and replace the removed fields with their replacements. For the list of removed fields, see the [changelog](https://github.com/redpanda-data/redpanda-operator/blob/release/v25.1.x/operator/CHANGELOG.md).

### [](#updated-versioning-scheme)Updated versioning scheme

An updated versioning scheme now better supports and tracks compatible Redpanda versions, ensuring smoother upgrades and improved compatibility management.

See also: [Kubernetes Compatibility](https://docs.redpanda.com/streaming/25.1/upgrade/k-compatibility/).

### [](#connectors-subchart-removed)Connectors subchart removed

The connectors subchart has been removed from the Helm chart because it is not officially supported.

> 💡 **TIP: Try Redpanda Connect**
>
> For a supported and scalable Kafka Connect alternative, consider using Redpanda Connect. For more information, see [Get Started](https://docs.redpanda.com/connect/get-started/).

## [](#redpanda-operator-v2-4-x)Redpanda Operator v2.4.x

[Changelog](https://github.com/redpanda-data/redpanda-operator/blob/release/v2.4.x/operator/CHANGELOG.md).

### [](#flux-disabled-by-default)Flux disabled by default

In version v2.3.x the `chartRef.useFlux` configuration was in beta and set to `true` by default. Starting from version v2.4.1, the `chartRef.useFlux:false` configuration is both GA and the default.

**Breaking change:** If you depend on Flux, explicitly set `chartRef.useFlux: true` in your configuration.

Example:

```yaml
spec:
  chartRef:
    useFlux: true
```

If you upgrade to v2.4.x from an older version in which Flux was explicitly enabled, Flux remains in use. If Flux was explicitly disabled, it remains disabled after an upgrade unless you explicitly enable it.

### [](#smarter-kubernetes-rolling-restarts-and-upgrades)Smarter Kubernetes rolling restarts and upgrades

This release improves how brokers are marked healthy, reducing unnecessary stalls during upgrades, especially under load.

### [](#ability-to-change-statefulset-replicas-without-restarting-brokers)Ability to change StatefulSet replicas without restarting brokers

Starting in v2.4.1, the Redpanda Operator allows you to increase or decrease the number of replicas in a StatefulSet without restarting existing brokers. This ability is useful for scaling your cluster up or down without downtime.

### [](#unified-versioning-for-the-redpanda-operator-helm-chart)Unified versioning for the Redpanda Operator Helm chart

Starting with Redpanda Operator v2.4.1, the Helm chart versioning has been streamlined so that the chart version is always identical to the Redpanda Operator’s version. The `version` field now matches the `appVersion` field.

This unified versioning approach simplifies the upgrade process, ensuring that you always deploy the chart corresponding to your desired version of the Redpanda Operator.

## [](#redpanda-operator-v2-3-x)Redpanda Operator v2.3.x

[Changelog](https://github.com/redpanda-data/redpanda-operator/blob/release/v2.3.x/operator/CHANGELOG.md).

### [](#declarative-schema-management)Declarative schema management

The Redpanda Operator now supports declarative schema management using the Schema custom resource, starting in version v2.3.0. This feature allows you to:

-   Define, create, and manage Avro, Protobuf, and JSON schemas declaratively.

-   Enforce schema compatibility and evolution policies directly in Kubernetes.

-   Automate schema lifecycle management alongside Redpanda deployments.


To learn more, see the [Schema custom resource documentation](https://docs.redpanda.com/streaming/25.1/manage/kubernetes/k-schema-controller/).

### [](#use-redpanda-operator-without-flux)Use Redpanda Operator without Flux

The Redpanda Operator now supports the `chartRef.useFlux` flag, giving you control over resource management, starting in version v2.3.0.

-   `chartRef.useFlux: false`: Directly manages resources within the Redpanda Operator, bypassing Flux.

-   `chartRef.useFlux: true`: Delegates Redpanda resource management to Flux controllers through HelmRelease resources.


This flag is in beta and set to `true` by default. If you want to use the Redpanda Operator without Flux, set `chartRef.useFlux: false` in your configuration.

## [](#redpanda-operator-v2-2-x)Redpanda Operator v2.2.x

### [](#declarative-user-and-acl-management)Declarative user and ACL management

The Redpanda Operator now supports declarative management of users and access control lists (ACLs) using the new User custom resource, starting in version v2.2.2. This feature allows you to:

-   Create and manage Redpanda users and their authentication settings.

-   Define and manage ACLs to control access to Redpanda resources.

-   Automatically reconcile changes to users and ACLs using the Redpanda Operator.


To learn more, see the [User custom resource documentation](https://docs.redpanda.com/streaming/25.1/manage/kubernetes/security/authentication/k-user-controller/).