redpanda-data · chrisseto · Apr 8, 2025 · Apr 8, 2025
@@ -170,7 +170,7 @@ tasks:
   sync:redpanda:chart:
     - task: sync:chart
       vars:
-        REF: charts/redpanda/v5.9.21
+        REF: charts/redpanda/v25.1.1-beta1
         LOCAL_DIR: charts/redpanda
         REMOTE_DIR: charts/redpanda
 
@@ -191,7 +191,7 @@ tasks:
   sync:console:chart:
     - task: sync:chart
       vars:
-        REF: charts/console/v3.0.0
+        REF: 4ece701cb9a4c6d99f930e745476b1c2757e7165 # charts/console/v3.0.0 with a corrected version
         LOCAL_DIR: charts/console
         REMOTE_DIR: charts/console
 

@@ -5,7 +5,129 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
 and is generated by [Changie](https://github.com/miniscruff/changie).
 
 
-## v5.9.21 - 2025-03-03
+## Unreleased
+### Added
+* Added a chart wide `podTemplate` field which may be used to control Pod attributes chart wide.
+
+  This field has a lower precedence than `statefulset.podTemplate` and
+  `post_install_job.podTemplate` but will still be merged with them.
+* `podTemplate`, `statefulset.podTemplate`, and `post_install_job.podTemplate` may now contain template expressions **with in string fields**
+
+  To compensate for some of the functionality that was lost with the removal of
+  fields like `extraVolumes`, we've upgraded `podTemplate` fields to support
+  templating. Rather than allowing full control over a structured value, we've
+  reduced the scope to only string fields. This is significantly more
+  maintainable and less error prone.
+
+  As an example, the below snippet will apply the release name as an annotation
+  to all Pods created by the chart.
+
+  ```yaml
+  podTemplate:
+    annotations:
+      "keys-cannot-be-templated": '{{ .Release.Name }}' # But values can!
+  ```
+
+  See `values.yaml` for additional examples.
+### Changed
+* Promoted the config-watcher sidecar into a real go binary that handles user management and simplifies cluster health checks so they no longer fail when the sole issue is that other nodes in the cluster are unavailable. Additionally the new sidecar subsumes the behavior of the `statefulset.sideCars.controllers` stanza which should now be specified via their own `enabled` flags.
+* `clusterDomain` now defaults to `cluster.local.` (A trialing `.` has been added) and the chart no longer adds trailing `.`'s to internal domains.
+
+  For users not experiencing issues with trailing `.`'s this change has no
+  effect. For users that have had issues with trailing `.`'s, it's now possible
+  to opt-out of this behavior by explicitly setting `clusterDomain` to `cluster.local`.
+
+  For users that override `clusterDomain`, copied a previous releases
+  values.yaml, or use the `--reuse-values` flag, trailing `.`'s will be tripped
+  from domains upon updating. This behavior may be opted into by appending a
+  `.` to `clusterDomain` prior to upgrading.
+* Bump AppVersion to v24.3.6 Redpanda release
+* Bump Redpanda operator side car container tag to `v2.3.7-24.3.6`.
+* `values.schema.json` is now "closed" (`additionalProperties: false`)
+
+  Any unexpected values will result in a validation error,previously they would
+  have been ignored.
+* Update Console depedency to latest version with breaking change. Please visit Console change-log.
+* The name of the container running redpanda is now always set to `redpanda`.
+* bumped `appVersion` to [v25.1.1](https://github.com/redpanda-data/redpanda/releases/tag/v25.1.1).
+### Removed
+* Connectors sub-chart integration.
+
+  The connectors chart may still be deployed separately, though it is not
+  officially support. If possible, it is recommended to migrate to redpanda
+  connect.
+* Removed the deprecated fields `license_key` and `license_secret_ref` in favor
+of `enterprise.license` and `enterprise.licenseSecretRef`, respectively.
+* `statefulset.securityContext`, `statefulset.sideCars.configWatcher.securityContext` have been removed.
+
+  These fields previously served as both PodSecurityContext and SecurityContext
+  across the entire chart which led to confusing semantics that couldn't be
+  fixed without breaking backwards compatiblity.
+
+  The top level `podTemplate` field may be used to control
+  PodSecurityContexts and SecurityContexts across the chart.
+* Fields that would be better served through `podTemplate` have been removed in favor of using `podTemplate`.
+
+  Removed fields:
+  - `nodeSelector` -> `podTemplate.spec.nodeSelector`
+  - `affinity` -> `podTemplate.spec.affinity`
+  - `tolerations` -> `podTemplate.spec.tolerations`
+  - `imagePullSecrets` -> `podTemplate.spec.imagePullSecrets`
+  - `statefulset.annotations` -> `statefulset.podTemplate.annotations`
+  - `statefulset.startupProbe` -> `statefulset.podTemplate.spec.containers[0].startupProbe`
+  - `statefulset.livenessProbe` -> `statefulset.podTemplate.spec.containers[0].livenessProbe`
+  - `statefulset.readinessProbe` -> `statefulset.podTemplate.spec.containers[1].readinessProbe`
+  - `statefulset.podAffinity` -> `statefulset.podTemplate.spec.affinity.podAffinity`
+  - `statefulset.nodeSelector` -> `statefulset.podTemplate.spec.nodeSelector`
+  - `statefulset.priorityClassName` -> `statefulset.podTemplate.spec.priorityClassName`
+  - `statefulset.tolerations` -> `statefulset.podTemplate.spec.tolerations`
+  - `statefulset.topologySpreadConstraints` -> `statefulset.podTemplate.spec.topologySpreadConstraints`
+  - `statefulset.terminationGracePeriodSeconds` -> `statefulset.podTemplate.spec.terminationGracePeriodSeconds`
+  - `statefulset.extraVolumes` -> `statefulset.podTemplate.spec.volumes`
+  - `statefulset.extraVolumesMounts` -> `statefulset.podTemplate.spec.containers[*].volumeMounts`
+  - `statefulset.initContainers.*.extraVolumesMounts` -> `statefulset.podTemplate.spec.initContainers[*].volumeMounts`
+  - `statefulset.initContainers.*.resources` -> `statefulset.podTemplate.spec.initContainers[*].resources`
+  - `statefulset.initContainers.extraInitContainers` -> `statefulset.podTemplate.spec.initContainers`
+  - `statefulset.sidecars.configWatcher.extraVolumeMounts` -> `statefulset.podTemplate.spec.containers[*].volumeMounts`
+  - `statefulset.sidecars.configWatcher.resources` -> `statefulset.podTemplate.spec.containers[*].resources`
+  - `statefulset.sidecars.configWatcher.securityContext` -> `statefulset.podTemplate.spec.containers[*].securityContext`
+  - `statefulset.sidecars.controllers.resources` -> `statefulset.podTemplate.spec.containers[*].resources`
+  - `statefulset.sidecars.controllers.securityContext` -> `statefulset.podTemplate.spec.containers[*].securityContext`
+  - `statefulset.sidecars.extraVolumeMounts` -> `statefulset.podTemplate.spec.containers[*].volumeMounts`
+  - `statefulset.sidecars.resources` -> `statefulset.podTemplate.spec.containers[*].resources`
+  - `statefulset.sidecars.securityContext` -> `statefulset.podTemplate.spec.containers[*].securityContext`
+### Fixed
+* Reverse order of applying resources to first create ClusterRole and then ClusterRoleBinding.
+  When Redpanda custom resource has enabled RBAC the reconciliation was blocked due
+  ClusterRoleBinding referencing not yet created ClusterRole.
+
+* Fixed an issue where not explicitly specifying a SASL auth mechanism when SASL is enabled caused Console to fail to start up.
+* Prevent broker nodes from restarting when solely the cluster replica amount changes
+
+## v25.1.1-beta1 - 2025-04-08
+### Added
+* Added a chart wide `podTemplate` field which may be used to control Pod attributes chart wide.
+
+  This field has a lower precedence than `statefulset.podTemplate` and
+  `post_install_job.podTemplate` but will still be merged with them.
+* `podTemplate`, `statefulset.podTemplate`, and `post_install_job.podTemplate` may now contain template expressions **with in string fields**
+
+  To compensate for some of the functionality that was lost with the removal of
+  fields like `extraVolumes`, we've upgraded `podTemplate` fields to support
+  templating. Rather than allowing full control over a structured value, we've
+  reduced the scope to only string fields. This is significantly more
+  maintainable and less error prone.
+
+  As an example, the below snippet will apply the release name as an annotation
+  to all Pods created by the chart.
+
+  ```yaml
+  podTemplate:
+    annotations:
+      "keys-cannot-be-templated": '{{ .Release.Name }}' # But values can!
+  ```
+
+  See `values.yaml` for additional examples.
 ### Changed
 * Promoted the config-watcher sidecar into a real go binary that handles user management and simplifies cluster health checks so they no longer fail when the sole issue is that other nodes in the cluster are unavailable. Additionally the new sidecar subsumes the behavior of the `statefulset.sideCars.controllers` stanza which should now be specified via their own `enabled` flags.
 * `clusterDomain` now defaults to `cluster.local.` (A trialing `.` has been added) and the chart no longer adds trailing `.`'s to internal domains.
@@ -20,11 +142,66 @@ and is generated by [Changie](https://github.com/miniscruff/changie).
   `.` to `clusterDomain` prior to upgrading.
 * Bump AppVersion to v24.3.6 Redpanda release
 * Bump Redpanda operator side car container tag to `v2.3.7-24.3.6`.
+* `values.schema.json` is now "closed" (`additionalProperties: false`)
+
+  Any unexpected values will result in a validation error,previously they would
+  have been ignored.
+* Update Console depedency to latest version with breaking change. Please visit Console change-log.
+* The name of the container running redpanda is now always set to `redpanda`.
+* bumped `appVersion` to [v25.1.1](https://github.com/redpanda-data/redpanda/releases/tag/v25.1.1).
+### Removed
+* Connectors sub-chart integration.
+
+  The connectors chart may still be deployed separately, though it is not
+  officially support. If possible, it is recommended to migrate to redpanda
+  connect.
+* Removed the deprecated fields `license_key` and `license_secret_ref` in favor
+of `enterprise.license` and `enterprise.licenseSecretRef`, respectively.
+* `statefulset.securityContext`, `statefulset.sideCars.configWatcher.securityContext` have been removed.
+
+  These fields previously served as both PodSecurityContext and SecurityContext
+  across the entire chart which led to confusing semantics that couldn't be
+  fixed without breaking backwards compatiblity.
+
+  The top level `podTemplate` field may be used to control
+  PodSecurityContexts and SecurityContexts across the chart.
+* Fields that would be better served through `podTemplate` have been removed in favor of using `podTemplate`.
+
+  Removed fields:
+  - `nodeSelector` -> `podTemplate.spec.nodeSelector`
+  - `affinity` -> `podTemplate.spec.affinity`
+  - `tolerations` -> `podTemplate.spec.tolerations`
+  - `imagePullSecrets` -> `podTemplate.spec.imagePullSecrets`
+  - `statefulset.annotations` -> `statefulset.podTemplate.annotations`
+  - `statefulset.startupProbe` -> `statefulset.podTemplate.spec.containers[0].startupProbe`
+  - `statefulset.livenessProbe` -> `statefulset.podTemplate.spec.containers[0].livenessProbe`
+  - `statefulset.readinessProbe` -> `statefulset.podTemplate.spec.containers[1].readinessProbe`
+  - `statefulset.podAffinity` -> `statefulset.podTemplate.spec.affinity.podAffinity`
+  - `statefulset.nodeSelector` -> `statefulset.podTemplate.spec.nodeSelector`
+  - `statefulset.priorityClassName` -> `statefulset.podTemplate.spec.priorityClassName`
+  - `statefulset.tolerations` -> `statefulset.podTemplate.spec.tolerations`
+  - `statefulset.topologySpreadConstraints` -> `statefulset.podTemplate.spec.topologySpreadConstraints`
+  - `statefulset.terminationGracePeriodSeconds` -> `statefulset.podTemplate.spec.terminationGracePeriodSeconds`
+  - `statefulset.extraVolumes` -> `statefulset.podTemplate.spec.volumes`
+  - `statefulset.extraVolumesMounts` -> `statefulset.podTemplate.spec.containers[*].volumeMounts`
+  - `statefulset.initContainers.*.extraVolumesMounts` -> `statefulset.podTemplate.spec.initContainers[*].volumeMounts`
+  - `statefulset.initContainers.*.resources` -> `statefulset.podTemplate.spec.initContainers[*].resources`
+  - `statefulset.initContainers.extraInitContainers` -> `statefulset.podTemplate.spec.initContainers`
+  - `statefulset.sidecars.configWatcher.extraVolumeMounts` -> `statefulset.podTemplate.spec.containers[*].volumeMounts`
+  - `statefulset.sidecars.configWatcher.resources` -> `statefulset.podTemplate.spec.containers[*].resources`
+  - `statefulset.sidecars.configWatcher.securityContext` -> `statefulset.podTemplate.spec.containers[*].securityContext`
+  - `statefulset.sidecars.controllers.resources` -> `statefulset.podTemplate.spec.containers[*].resources`
+  - `statefulset.sidecars.controllers.securityContext` -> `statefulset.podTemplate.spec.containers[*].securityContext`
+  - `statefulset.sidecars.extraVolumeMounts` -> `statefulset.podTemplate.spec.containers[*].volumeMounts`
+  - `statefulset.sidecars.resources` -> `statefulset.podTemplate.spec.containers[*].resources`
+  - `statefulset.sidecars.securityContext` -> `statefulset.podTemplate.spec.containers[*].securityContext`
 ### Fixed
 * Reverse order of applying resources to first create ClusterRole and then ClusterRoleBinding.
   When Redpanda custom resource has enabled RBAC the reconciliation was blocked due
   ClusterRoleBinding referencing not yet created ClusterRole.
 
+* Fixed an issue where not explicitly specifying a SASL auth mechanism when SASL is enabled caused Console to fail to start up.
+* Prevent broker nodes from restarting when solely the cluster replica amount changes
 
 ## v5.9.20 - 2025-02-06
 ### Changed

@@ -23,11 +23,11 @@ type: application
 # The chart version and the app version are not the same and will not track
 # together. The chart version is a semver representation of changes to this
 # chart.
-version: 5.9.21
+version: 25.1.1-beta1
 
 # The app version is the default version of Redpanda to install.
 # ** NOTE for maintainers: please ensure the artifacthub image annotation is updated before merging
-appVersion: v24.3.6
+appVersion: v25.1.1
 
 # kubeVersion must be suffixed with "-0" to be able to match cloud providers
 # kubernetes versions like "v1.23.8-gke.1900". Their suffix is interpreted as a
@@ -37,12 +37,9 @@ kubeVersion: ">= 1.25.0-0"
 dependencies:
   - name: console
     condition: console.enabled
-    version: ">=0.5 <1.0"
-    repository: https://charts.redpanda.com
-  - name: connectors
-    condition: connectors.enabled
-    version: ">=0.1.2 <1.0"
+    version: ">=3.0.0-0"
     repository: https://charts.redpanda.com
+    alias: console
 
 icon: https://images.ctfassets.net/paqvtpyf8rwu/3cYHw5UzhXCbKuR24GDFGO/73fb682e6157d11c10d5b2b5da1d5af0/skate-stand-panda.svg
 sources:
@@ -56,6 +53,6 @@ annotations:
       url: https://helm.sh/docs/intro/install/
   artifacthub.io/images: |
     - name: redpanda
-      image: docker.redpanda.com/redpandadata/redpanda:v24.3.6
+      image: docker.redpanda.com/redpandadata/redpanda:v25.1.1
     - name: busybox
       image: busybox:latest