Docs Self-Managed Get Started What’s New Helm Charts What’s New in the Helm Charts This topic includes new content and significant changes in the Redpanda and Redpanda Console Helm charts. For a complete list of all updates, see: Changelog for the Redpanda chart. Changelog for the Redpanda Console chart. See also: What’s New in Redpanda Kubernetes Compatibility Upgrade Redpanda in Kubernetes Redpanda chart v25.1.1 (GA) Changelog. Redpanda Console v3 This version deploys Redpanda Console v3, which includes unified authentication and authorization between the Console and Redpanda, including user impersonation. For more information, see Authentication in Redpanda Console. This version does not support Redpanda Console v2. Before upgrading, migrate your Redpanda Console v2 configuration to the new v3 format. For more information, see Migrate to Redpanda Console v3.0.0. Schema validation The Redpanda Helm chart now includes stricter schema validation to ensure configurations conform to expected standards. With schema validation enabled, you must ensure your overrides include valid fields. Removed fields The following deprecated fields have been removed from the Helm values. Before upgrading, review your configurations and replace the removed fields with their replacements. For the list of removed fields, see the changelog. 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. Kafka Connect integration removed from Helm chart Starting with version 25.1.x of the Redpanda Helm chart, Kafka Connect is no longer bundled as a subchart. If you require Kafka Connect, you must install the connectors Helm chart separately after deploying Redpanda. For instructions, see Deploy Kafka Connect in Kubernetes. To check if you’re currently using Redpanda’s managed Kafka Connect, run: kubectl get pod -l app.kubernetes.io/name=connectors --namespace <namespace> For stream processing on Kubernetes, consider using Redpanda Connect. It offers a simplified, scalable alternative to Kafka Connect for building data pipelines with a supported Kubernetes integration. Reference Kubernetes Secrets and ConfigMaps for Redpanda cluster configuration You can now set any Redpanda cluster configuration property using the new extraClusterConfiguration field. This allows you to reference values from Kubernetes Secrets or ConfigMaps. For example, use this field to inject sensitive credentials or reuse shared configurations across features like Tiered Storage, Iceberg, and disaster recovery. This enhancement improves: Security: Avoid hardcoding secrets in Helm values or manifests. Reusability: Centralize common values used by multiple features. Maintainability: Better integrate with GitOps workflows and Kubernetes-native resource management. See Set Redpanda cluster properties from Kubernetes Secrets or ConfigMaps. Redpanda chart v5.10.x Ability to change StatefulSet replicas without restarting brokers Starting in v5.10.1, the Redpanda Helm chart 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. Redpanda chart v5.9.x Sidecar for broker decommissioning and PVC cleanup Version v5.9.21 of the Redpanda Helm chart introduces two new sidecar-based controllers to manage broker decommissioning and persistent volume cleanup: BrokerDecommissioner: Detects non-graceful broker failures, such as node crashes, and triggers automated decommissioning. PVCUnbinder: Ensures persistent volume claims (PVCs) are properly unbound and cleaned up after broker removal. The NodeWatcher and Decommission controllers are deprecated and replaced by a single sidecar. To enable the equivalent of the controllers, set the enabled flag to true in your Redpanda custom resource. For example: statefulset: sideCars: brokerDecommissioner: enabled: true decommissionAfter: 60s pvcUnbinder: enabled: true unbindAfter: 60s rbac: enabled: true If you previously relied on the NodeWatcher or Decommission controllers, switch to the new sidecars for improved stability and control. Back to top × Simple online edits For simple changes, such as fixing a typo, you can edit the content directly on GitHub. Edit on GitHub Or, open an issue to let us know about something that you want us to change. Open an issue Contribution guide For extensive content updates, or if you prefer to work locally, read our contribution guide . Was this helpful? thumb_up thumb_down group Ask in the community mail Share your feedback group_add Make a contribution 🎉 Thanks for your feedback! Operator Introduction to Redpanda