You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: charts/redpanda/CHANGELOG.md
+178-1Lines changed: 178 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,129 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
5
5
and is generated by [Changie](https://github.com/miniscruff/changie).
6
6
7
7
8
-
## v5.9.21 - 2025-03-03
8
+
## Unreleased
9
+
### Added
10
+
* Added a chart wide `podTemplate` field which may be used to control Pod attributes chart wide.
11
+
12
+
This field has a lower precedence than `statefulset.podTemplate` and
13
+
`post_install_job.podTemplate` but will still be merged with them.
14
+
*`podTemplate`, `statefulset.podTemplate`, and `post_install_job.podTemplate` may now contain template expressions **with in string fields**
15
+
16
+
To compensate for some of the functionality that was lost with the removal of
17
+
fields like `extraVolumes`, we've upgraded `podTemplate` fields to support
18
+
templating. Rather than allowing full control over a structured value, we've
19
+
reduced the scope to only string fields. This is significantly more
20
+
maintainable and less error prone.
21
+
22
+
As an example, the below snippet will apply the release name as an annotation
23
+
to all Pods created by the chart.
24
+
25
+
```yaml
26
+
podTemplate:
27
+
annotations:
28
+
"keys-cannot-be-templated": '{{ .Release.Name }}'# But values can!
29
+
```
30
+
31
+
See `values.yaml` for additional examples.
32
+
### Changed
33
+
* 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.
34
+
* `clusterDomain` now defaults to `cluster.local.` (A trialing `.` has been added) and the chart no longer adds trailing `.`'s to internal domains.
35
+
36
+
For users not experiencing issues with trailing `.`'s this change has no
37
+
effect. For users that have had issues with trailing `.`'s, it's now possible
38
+
to opt-out of this behavior by explicitly setting `clusterDomain` to `cluster.local`.
39
+
40
+
For users that override `clusterDomain`, copied a previous releases
41
+
values.yaml, or use the `--reuse-values` flag, trailing `.`'s will be tripped
42
+
from domains upon updating. This behavior may be opted into by appending a
43
+
`.`to `clusterDomain` prior to upgrading.
44
+
* Bump AppVersion to v24.3.6 Redpanda release
45
+
* Bump Redpanda operator side car container tag to `v2.3.7-24.3.6`.
46
+
* `values.schema.json` is now "closed" (`additionalProperties: false`)
47
+
48
+
Any unexpected values will result in a validation error,previously they would
49
+
have been ignored.
50
+
* Update Console depedency to latest version with breaking change. Please visit Console change-log.
51
+
* The name of the container running redpanda is now always set to `redpanda`.
52
+
* bumped `appVersion` to [v25.1.1](https://github.com/redpanda-data/redpanda/releases/tag/v25.1.1).
53
+
### Removed
54
+
* Connectors sub-chart integration.
55
+
56
+
The connectors chart may still be deployed separately, though it is not
57
+
officially support. If possible, it is recommended to migrate to redpanda
58
+
connect.
59
+
* Removed the deprecated fields `license_key` and `license_secret_ref` in favor
60
+
of `enterprise.license` and `enterprise.licenseSecretRef`, respectively.
61
+
* `statefulset.securityContext`, `statefulset.sideCars.configWatcher.securityContext` have been removed.
62
+
63
+
These fields previously served as both PodSecurityContext and SecurityContext
64
+
across the entire chart which led to confusing semantics that couldn't be
65
+
fixed without breaking backwards compatiblity.
66
+
67
+
The top level `podTemplate` field may be used to control
68
+
PodSecurityContexts and SecurityContexts across the chart.
69
+
* Fields that would be better served through `podTemplate` have been removed in favor of using `podTemplate`.
* Reverse order of applying resources to first create ClusterRole and then ClusterRoleBinding.
101
+
When Redpanda custom resource has enabled RBAC the reconciliation was blocked due
102
+
ClusterRoleBinding referencing not yet created ClusterRole.
103
+
104
+
* Fixed an issue where not explicitly specifying a SASL auth mechanism when SASL is enabled caused Console to fail to start up.
105
+
* Prevent broker nodes from restarting when solely the cluster replica amount changes
106
+
107
+
## v25.1.1-beta1 - 2025-04-08
108
+
### Added
109
+
* Added a chart wide `podTemplate` field which may be used to control Pod attributes chart wide.
110
+
111
+
This field has a lower precedence than `statefulset.podTemplate` and
112
+
`post_install_job.podTemplate`but will still be merged with them.
113
+
* `podTemplate`, `statefulset.podTemplate`, and `post_install_job.podTemplate` may now contain template expressions **with in string fields**
114
+
115
+
To compensate for some of the functionality that was lost with the removal of
116
+
fields like `extraVolumes`, we've upgraded `podTemplate` fields to support
117
+
templating. Rather than allowing full control over a structured value, we've
118
+
reduced the scope to only string fields. This is significantly more
119
+
maintainable and less error prone.
120
+
121
+
As an example, the below snippet will apply the release name as an annotation
122
+
to all Pods created by the chart.
123
+
124
+
```yaml
125
+
podTemplate:
126
+
annotations:
127
+
"keys-cannot-be-templated": '{{ .Release.Name }}' # But values can!
128
+
```
129
+
130
+
See `values.yaml` for additional examples.
9
131
### Changed
10
132
* 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.
11
133
* `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).
20
142
`.`to `clusterDomain` prior to upgrading.
21
143
* Bump AppVersion to v24.3.6 Redpanda release
22
144
* Bump Redpanda operator side car container tag to `v2.3.7-24.3.6`.
145
+
* `values.schema.json` is now "closed" (`additionalProperties: false`)
146
+
147
+
Any unexpected values will result in a validation error,previously they would
148
+
have been ignored.
149
+
* Update Console depedency to latest version with breaking change. Please visit Console change-log.
150
+
* The name of the container running redpanda is now always set to `redpanda`.
151
+
* bumped `appVersion` to [v25.1.1](https://github.com/redpanda-data/redpanda/releases/tag/v25.1.1).
152
+
### Removed
153
+
* Connectors sub-chart integration.
154
+
155
+
The connectors chart may still be deployed separately, though it is not
156
+
officially support. If possible, it is recommended to migrate to redpanda
157
+
connect.
158
+
* Removed the deprecated fields `license_key` and `license_secret_ref` in favor
159
+
of `enterprise.license` and `enterprise.licenseSecretRef`, respectively.
160
+
* `statefulset.securityContext`, `statefulset.sideCars.configWatcher.securityContext` have been removed.
161
+
162
+
These fields previously served as both PodSecurityContext and SecurityContext
163
+
across the entire chart which led to confusing semantics that couldn't be
164
+
fixed without breaking backwards compatiblity.
165
+
166
+
The top level `podTemplate` field may be used to control
167
+
PodSecurityContexts and SecurityContexts across the chart.
168
+
* Fields that would be better served through `podTemplate` have been removed in favor of using `podTemplate`.
0 commit comments