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
fix: emit SCRAM-SHA512 sasl_mechanism the kafka-backup binary accepts
The kafka-backup binary's config parser only accepts SCRAM-SHA512 (no
hyphen before the digits), but both config adapters wrote the CRD-style
SCRAM-SHA-512 into generated ConfigMaps, so every backup or restore job
using authentication.type: scram-sha-512 failed on startup with
"unknown variant `SCRAM-SHA-512`".
The mechanism string now lives in a single shared constant used by both
the backup and restore adapters.
Verified end-to-end in kind: Strimzi 0.46.1 with a SCRAM-SHA-512
listener, MinIO S3 storage, backup and restore jobs both complete and
round-trip 100 records.
Fixes#35
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: CHANGELOG.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,12 @@
2
2
3
3
All notable changes to this project will be documented in this file.
4
4
5
+
## 0.2.11 - 2026-07-03
6
+
7
+
### Fixed
8
+
9
+
- Write `sasl_mechanism: SCRAM-SHA512` (no hyphen before the digits) into generated backup and restore ConfigMaps. The kafka-backup binary's config parser only accepts `SCRAM-SHA512`, so jobs for resources using `authentication.type: scram-sha-512` failed on startup with `unknown variant 'SCRAM-SHA-512'`. Fixes [#35](https://github.com/osodevops/strimzi-backup-operator/issues/35).
0 commit comments