Andrey Kolkov 0d918e1f91 fix(backups): resolve Kafka backup client image from the target broker ...

The Kafka metadata strategy pinned kafkaBackupClientImage to an upstream
Strimzi tag with no producer: nothing stamped it and Renovate does not
manage helm-values, so it drifted from the broker version the operator
provisions. A dedicated small client image (the sibling curl-only drivers'
follow-up) is not viable here because the driver runs the Kafka Admin-API
CLI, which only the broker image ships.

Resolve the client image from a live broker pod of the target Strimzi Kafka
at reconcile time instead, so the CLI always matches the broker (any version
the operator picks, not only the chart default), and record it on the Backup
so cleanup can reuse it once the source cluster is gone. The chart no longer
pins the image; the strategy template renders it as the .ClientImage
placeholder the controller fills.

Signed-off-by: Andrey Kolkov <androndo@gmail.com>
Assisted-by: LLM

2026-09-10 22:23:52 +04:00

..

default_objects_gate_test.yaml

fix(backupstrategy-controller): repair the bucket credentials Secret from the gate, not a chart fail

2026-08-07 11:10:41 +02:00

deployment_test.yaml

test(backupstrategy-controller): anchor the metrics-absence guard to its container

2026-08-07 15:08:56 +03:00

endpoint_form_test.yaml

fix(backups): derive default S3 endpoint from the provisioned bucket

2026-07-15 19:11:36 +05:00

rendering_test.yaml

fix(backups): resolve Kafka backup client image from the target broker

2026-09-10 22:23:52 +04:00

strategy_redis_test.yaml

fix(backups): delete Redis backup objects on cleanup and size the restore Pod

2026-09-09 12:19:02 +04:00