All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and is generated by Changie.
-
Bumped internal redpanda chart to v5.9.19.
chartRef
now defaults to v5.9.19. WhenuseFlux
isfalse
, the equivalent of chart v5.9.19 will be deployed. -
Bumped the internal chart version to v5.9.20.
-
Removed bundled FluxCD controllers, bundled FluxCD CRDs, and support for delegating control to FluxCD.
Previously reconciled FluxCD resources (
HelmRepository
,HelmRelease
) will NOT be garbage collected upon upgrading. If the operator is coexisting with a FluxCD installation, please take care to manually remove the left over resources.chartRef.useFlux: true
andchartRef.chartVersion
are no longer supported. The controller will log errors and abort reconcilation until the fields are unset. Ensure that both have been removed from allRedpanda
resources before upgrading.All other
chartRef
fields are deprecated and are no longer referenced.helmRelease
,helmReleaseReady
,helmRepository
,helmRepositoryReady
, andupgradeFailures
are no longer set onRedpandaStatus
, similar to their behavior whenuseFlux: false
was set. -
gcr.io/kubebuilder/kube-rbac-proxy
container is deprecated and has been removed from the Redpanda operator helm chart. The same ports will continue to serve metrics using kubebuilder's built in RBAC.
Any existing prometheus rules don't need to be adjusted.
For more details see: kubernetes-sigs/kubebuilder#3907
-
Usage of
tpl
andinclude
now function as expected whenuseFlux: false
is set.{{ (get (fromJson (include "redpanda.Fullname" (dict "a" (list .)))) "r") }}
would previously failure with fairly arcane errors.Now, the above example will correctly render to a string value. However, syntax errors and the like are still reported in an arcane fashion.
-
Toggling
useFlux
, in either direction, no longer causes the bootstrap user's password to be regenerated.Manual mitigation steps are available here.
-
Users in air-gapped environments that cannot access the official Redpanda Helm Chart repository (
https://charts.redpanda.com/
) can now specify an alternative Helm chart repository using thehelm-repository-url
flag. In the Redpanda Operator Helm chart, this flag is not exposed as an option in the Helm values. Instead, it must be set as an input in theadditionalCmdFlags
array.The given repository must include the following charts:
- Redpanda
- Console
- Connectors
-
Added
resources.limits
andresources.requests
as an alternative method of managing the redpanda container's resources.When both
resources.limits
andresources.requests
are specified, the redpanda container'sresources
will be set to the provided values and all other keys ofresources
will be ignored. Instead, all other values will be inferred from the limits and requests.This allows fine grain control of resources. i.e. It is now possible to set CPU requests without setting limits:
resources: limits: {} # Specified but no cpu or memory values provided requests: cpu: 5 # Only CPU requests
- For any user that is mirroring configurator image (air-gapped environment) and changes entrypoint
or wraps configurator with additional script the following constraint need to be meet:
- set the following flags
- to change the container repository set
--configurator-base-image=my.repo.com/configurator
flag - to change the container tag set
--configurator-tag=XYZ
flag
- to change the container repository set
- image needs to supports the entrypoint
redpanda-operator configure
as it is the default one
- set the following flags
- Value's merging no longer writes files to disk which prevents the operator from eating disk space when the reconciliation loop is run in rapid succession
- Fixed slice out of bounds panics when using the fs-validator and
useFlux: false