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
Prior to this commit the operator's chart incorrect referenced a non-existent
`Role` for the permissions of rack awareness. As helm loves to swallow errors,
this went unnoticed until reported by an end user.
This commit corrects the mistake and adds a regression acceptance test.
Copy file name to clipboardExpand all lines: operator/CHANGELOG.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -95,6 +95,9 @@ This is required to ensure that a pre-existing sts can roll over to new configur
95
95
* Setting `serviceAccount.create` to `false` no longer prevents the Kubernetes ServiceAccountToken volume from being mounted to the operator Pod.
96
96
* updated operator v1 to ignore "cluster.redpanda.com/node-pool-spec" annotation for pod rolls. previously, under certain conditions, the operator started rolling pods if this annotation changed - but there is no need to do so.
97
97
* Added the missing `https` port to the operator Pod that was referenced by the [`ServiceMonitor`](https://github.com/redpanda-data/redpanda-operator/blob/4e34c5ea79b00fa0caeda64955e3291666194274/operator/chart/servicemonitor.go#L42)
98
+
*`get` permissions on `Node` resources is now correctly configured by default.
99
+
100
+
`--set rbac.createAdditionalControllerCRs=true` is no longer required for rackawareness to work.
0 commit comments