Invalid cluster.id in: /var/lib/kafka/data-0/kafka-log0/meta.properties

[lyd100822]

strimzi creates a kafka cluster and stores the configuration deleteClaim: false. After deleting the cluster, the pvc is retained. After creating it again, it reports that the cluster id is inconsistent, and the stored pvc id keeps changing. Sometimes broker 012, sometimes controller 012

[lyd100822]

The versions used are operator version 0.46.0, kafka 4.0.0, and k8s version 1.26.

[ppatierno]

I think you can find more info here https://github.com/orgs/strimzi/discussions/10082#discussioncomment-10086245

[lyd100822]

I think you can find more info here https://github.com/orgs/strimzi/discussions/10082#discussioncomment-10086245

I found that deleting meta.properties from all kafka-related PVCs, such as data-0-kafka-cluster-broker-0, etc. can solve this problem. Why doesn't the zooKeeper mode have this problem, and the old clusterid is used, while the kraft mode generates a new clusterid every time it is created?

[scholzj]

This is desired behaviour - Kafka protects itself this way from joining some other cluster. If you are intentionally trying to recover an existing cluster, you have to set the cluster id in the status of the Kafka resource (look for other discussions and issues for more detailed guidance). If you are not trying to recover a previously existing cluster, you should delete the PVCs first (or use a different name for the Kafka CR).

ZooKeeper did not have this issue because ZooKeeper is something completely different from KRaft and the cluster ID was handled in a completely different way.