Federico Valeri
Federico Valeri
@rlanhellas thanks for looking into this. When I created the report, I didn't have much time to do investigation, but the issue was consistent for me. Now, I've changed my...
> This might need to be documented, but it should not be fixed by reading any cluster IDs from the volumes. Definitely, because the current documented procedure is broken: https://strimzi.io/docs/operators/latest/deploying#proc-cluster-recovery-volume-str.
@scholzj I'm trying the KRaft volume recovery procedure with the status update as you suggested. It ultimately works, but it's not so nice. Let's say we have Kafka volumes binding...
Adding [cluster-op.log](https://github.com/user-attachments/files/17411553/cluster-op.log) after cluster recreation and `.status.clusterId` patch.
> Create the Kafka CR paused Ok, let me try that. > The main challenge is IMHO how to get the cluster Id if you don't have it We can...
Ok, that worked nicely, thank @scholzj. Going to write something down for the doc update, and then we can refine in the PR.
> The default value of -1 means that this will be set to the configured value of remote.log.manager.thread.pool.size, if available; otherwise, it defaults to 10 This is a bit confusing...
@satishd thanks for the feedback. Latest commit should address your request.
Test failures are unrelated. They work locally and are reported as flaky.
Trying to address in #10921.