Subject:
Issues with the Redpanda v2.1.19-24.1.2 Operator - Do Not Use
Summary:
Issues with version 2.1.19-24.1.2 of the Redpanda Operator and versions 0.4.23 of the Redpanda Helm Chart can cause the value for cloud_storage_enabled to become unset, potentially causing issues with cloud storage for impacted customers.
Severity:
Medium
Redpanda Products Affected:
Redpanda Self Hosted customers using the Operator or Helm Chart
Releases Affected:
Operator Version 2.1.19-24.1.2, Helm Version 0.4.23
Impact:
If using the impacted operator or helm version, and using tiered storage the value for cloud_storage_enabled becomes unset leading to issues using cloud storage, and to this value being constantly overwritten.
Immediate Action Required:
Verify if you are impacted by answering the below questions, and if you answer yes to all of them, you could be impacted.
- Do you use the Redpanda Operator or Helm Chart?
- Are you using Tiered Storage?
- Are you using version 2.1.19-24.1.2 of the Redpanda Operator or version 0.4.23 of the Redpanda Helm Chart
If impacted, complete the steps in the Action Required section below.
Action Required:
Affected users need to:
- Update to the latest CRDs:
kubectl kustomize "https://github.com/redpanda-data/redpanda-operator//src/go/k8s/config/crd?ref=v2.1.20-24.1.2" | kubectl apply --server-side -f -
- Update to the latest operator version:
- If using helm to manage the operator’s deployment:
helm repo update repanda && helm upgrade RELEASENAME redpanda/operator --version 'v0.4.24' (Assume helm was used to install the operator)
- Otherwise manually kubectl edit the operator’s deployment and update the image tag to v2.1.20-24.1.2
- As a safety precaution, double check the value of cloud_storage_enabled on all redpanda resources. Either a boolean or stringified boolean are acceptable ("true", "false", true, false).
rpk cluster config get cloud_storage_enabled
Users will want to avoid using the impacted versions of the Operator or Helm chart to avoid the issue. You can upgrade directly to Operator version 2.1.20 skipping the affected operator without issue.
Addressed by:
The below versions of the Redpanda Operator and Redpanda Helm Chart listed resolve this issue.
- Helm chart: https://github.com/redpanda-data/helm-charts/releases/tag/operator-0.4.24 or greater.
- Operator release: https://github.com/redpanda-data/redpanda-operator/releases/tag/v2.1.20-24.1.2 or greater.
Questions? If you have any questions on this TSB, or need further guidance, please contact support@redpanda.com