Suspending `KafkaBackup` does not suspend the underlying CronJob

[markediez]

https://github.com/osodevops/strimzi-backup-operator/blob/main/src/reconcilers/backup.rs#L99C13-L99C21

If I set spec.schedule.suspend = true, the previous cronjobs that the KafkaBackup resource created still has suspend: false. It results in unwanted kafka backup runs based on the schedule.

[sionsmith]

Thanks for the report @markediez — confirmed. The reconciler only applied the CronJob when the schedule was not suspended, so flipping spec.schedule.suspend to true never reached the already-created CronJob and it kept firing on its old schedule.

This is fixed in #25: the CronJob is now applied whenever a schedule is set, so the suspend flag propagates to the live resource on the next reconcile. While suspended, the KafkaBackup status also reports a BackupSuspended condition and clears nextScheduledBackup.

The fix will ship in v0.2.7 once the PR merges. Could you re-test on that release and confirm the CronJob gets suspend: true (and no further backup runs) after suspending your KafkaBackup? If you still see unwanted runs, please reopen with the operator logs.

[markediez]

I can confirm that updating the suspend value in KafkaBackup properly updates the CronJob as well. Thanks!