Unreleased - YYYY-MM-DD
5.9.10 - 2024-11-14
- All occurrence of External Domain execution via tpl function
- Calculating Service typed LoadBalancer annotation based on external addresses (even single one)
- Fix connecting to the schema registry via rpk on nodes for versions of rpk that support a node-level rpk stanza.
5.9.9 - 2024-10-24
- Strategic merge of Pod volumes and Container volumeMounts
- By default auto mount is disabled in ServiceAccount and Statefulset PodSpec
- Mount volume similar to auto mount functionality for ServiceAccount token when sidecar controllers are enabled
- Passing console extra volume and volume mount in Redpanda chart
- implements
time.ParseDuration
in gotohelm (with limitations) - updates the transpilation of
MustParseDuration
to properly re-serialize the provided duration
5.9.8 - 2024-10-23
- Bump Redpanda app version
- Increased the memory limits of
bootstrap-yaml-envsubst
to prevent hangs on aarch64 #1564.
5.9.7 - 2024-10-14
- Bump Redpanda app version
5.9.6 - 2024-10-09
- Added the ability to override the name of the bootstrap user created when SASL authentication is enabled. #1547
- The minimum Kubernetes version has been bumped to
1.25.0
- Chart render failures in tooling compiled with go < 1.19 (e.g. helm 3.10.x) have been fixed.
-
post_upgrade_job.*
, and the post-upgrade job itself, has been removed. All it's functionality has been consolidated into thepost_install_job
, which actually runs on both post-install and post-upgrade.The consolidated job now runs the redpanda-operator image, which may be controlled the same way as the additional controllers:
statefulset.controllers.{image,repository}
.
5.9.5 - 2024-09-26
- Bump Redpanda container tag/application version #1543
- Connectors deployment #1543
5.9.4 - 2024-09-17
-
Cluster configurations are no longer include in
redpanda.yaml
or the Redpanda Statefulset's configuration hash.This change makes it possible to update cluster configurations without initiating a rolling restart of the entire cluster.
As has always been the case, users should consult
rpk cluster config status
to determine if a rolling restart needs to be manually performed due to cluster configuration changes.Cases requiring manual rolling restarts may increase as fewer chart operations will initiate rolling restart of the cluster.
- Fix initialization of configurations using RestToConfig when the passed in rest.Config contain on-disk value files.
-
All zero, empty, or default cluster configurations have been removed from
values.yaml
in favor of letting redpanda determine what the defaults will be.Documentation of cluster configurations has also been removed in favor of linking to Redpanda's docs.
5.9.3 - 2024-09-11
- Add basic bootstrap user support (#1513)
- When specified,
truststore_file
is no longer propagated to client configurations. - If provided,
config.cluster.default_topic_replications
is now respected regardless of the value ofstatefulset.replicas
.
5.9.1 - 2024-8-19
- The
truststores
projected volume no longer duplicates entries when the same trust store is specified across multiple TLS configurations.
5.9.0 - 2024-08-09
post_install_job.podTemplate
andpost_upgrade_job.podTemplate
have been added, which allow overriding various aspects of the correspondingcorev1.PodTemplate
. Notably, this field may be used to set labels and annotations on the Pod produced by the Job which was not previously possible.statefulset.podTemplate
has benefited from the above additions as well.statefulset.podTemplate.spec.securityContext
andstatefulset.podTemplate.spec.containers[*].securityContext
may be used to set/override the pod and container security contexts respectively.appProtocol
added to thelisteners.admin
configuration
- The container name of the post-upgrade job is now statically set to
post-upgrade
to facilitate strategic merge patching. - The container name of the post-install job is now statically set to
post-install
to facilitate strategic merge patching. statefulset.securityContext
,statefulset.podSecurityContext
,post_upgrade_job.securityContext
, andpost_install_job.securityContext
have all been deprecated due to historically incorrect and confusing behavior. The desire to preserve backwards compatibility and not suddenly change sensitive fields has left us unable to cleanly correct said issues.{statefulset,post_upgrade_job,post_install_job}.podTemplate
may be used to override either the Pod or Container security context.
5.8.15 - 2024-08-08
- Bump Redpanda version due to a bug in Redpanda
- Fix mechanism check in superuser file creation
5.8.14 - 2024-08-07
- unset
status
andcreationTimestamp
before rendering resource
- Convert connectors to go
- Bump redpanda, connectors, operator and console helm chart application version
- Fix Redpanda node configuration generation, so that rpk can parse it
- Fix volume mounts in mTLS setup
- Correct boolean coalescing
5.8.13 - 2024-07-25
- Updated
appVersion
tov24.1.11
- Fixed a regression where
post_upgrade_job
would fail if TLS on the admin listener was disabled but hadcert
set to an invalid cert (e.g.""
) - Fixed mTLS configurations between Redpanda and Console #1402
- Fixed a typo in
statefulset.securityContext.allowPriviledgeEscalation
. Both the correct and typoed name will be respected with the correct spelling taking precedence. #1413
- Validation of
issuerRef
has been removed to permit external Issuers. #1432
5.8.12 - 2024-07-10
-
image.repository
longer needs to be the default value of"docker.redpanda.com/redpandadata/redpanda"
to respect version checks ofimage.tag
(#1334). -
post_upgrade_job.extraEnv
andpost_upgrade_job.extraEnvFrom
no longer accept string inputs.Previously, they accepted either strings or structured fields. As the types of this chart are reflected in the operator's CRD, we are bound by the constraints of Kubernetes' CRDs, which do not support fields with multiple types. We also noticed that the CRD requires these fields to be structured types rather than strings. Too minimize the divergences between the two, we've opted to drop support for string inputs here but preserve them elsewhere.
Updating these fields, if they are strings, is typically a case of needing to remove
|-
's from one's values file.Before:
post_upgrade_job: extraEnv: |- - name: SPECIAL_LEVEL_KEY valueFrom: configMapKeyRef: name: special-config key: special.how
After:
post_upgrade_job: extraEnv: - name: SPECIAL_LEVEL_KEY valueFrom: configMapKeyRef: name: special-config key: special.how
If you were using a templated value and would like to see it added back, please file us an issue and tell us about your use case!
- Numeric node/broker configurations are now properly transcoded as numerics.
Unreleased - YYYY-MM-DD
0.4.32 - 2024-10-31
- Strategic merge of Pod volumes
- Add new Schema custom resource RBAC rules
- The minimum Kubernetes version has been bumped to
1.25.0
- Bump operator version v2.2.5-24.2.7
- By default auto mount is disabled in ServiceAccount and Deployment PodSpec
- Mount volume similar to auto mount functionality for ServiceAccount token
--configurator-tag
now correctly falls back to.appVersion
0.4.31 - 2024-10-7
- Bump operator version v2.2.4-24.2.5
0.4.30 - 2024-09-17
- Add RBAC rules for the operator chart so it can manage users
0.4.29 - 2024-09-11
- Allow to overwrite
appsv1.Deployment.Spec.PodTemplate
- Bump operator version v2.2.2-24.2.4
- Translate operator helm chart to go.
0.4.28 - 2024-08-23
- Bump operator version v2.2.0-24.2.2
0.4.27 - 2024-08-08
- Bump operator version v2.1.29-24.2.2
0.4.26 - 2024-08-07
- Bump operator version v2.1.28-24.2.1
- Fix e2e operator tests
0.4.25 - 2024-07-17
- Updated
appVersion
tov2.1.26-24.1.9
- Added missing permissions for the NodeWatcher controller (
rbac.createAdditionalControllerCRs
)
Unreleased - YYYY-MM-DD
- The minimum Kubernetes version has been bumped to
1.25.0
- By default auto mount is disabled in ServiceAccount and Deployment PodSpec
0.1.13 - 2024-09-26
- Test pod name will be stable (without randomization) #1541
- Update connectors container tag/application version #1541
Unreleased - YYYY-MM-DD
- By default auto mount is disabled in ServiceAccount and Deployment PodSpec
0.7.30 - 2024-10-14
- Add Enabled flag that is used in Redpanda chart
- Add test example for oidc configuration #1503
- Bump Console app version
- Align Console init container default value
- The minimum Kubernetes version has been bumped to
1.25.0
- License json tag to correctly set Console license #1510
0.7.29 - 2024-08-19
- Fixed empty tag for the console image if tag is not overridden in values #1476
0.7.28 - 2024-08-08
- Fixed kubeVersion to be able to deploy on AWS EKS clusters.
Unreleased - YYYY-MM-DD
initContainers.extraInitContainers
is now pre-processed as YAML by the chart. Invalid YAML will instead be rendered as an error messages instead of invalid YAML.
- Support for Kubernetes versions < 1.21 have been dropped.
Unreleased - YYYY-MM-DD
- Parameter to configure submitting anonymous telemetry data
- Bump Connect app version to 4.39.0
- Refreshed chart and migrated from the old standalone repo