Replies: 5 comments
|
Some suspicios controller logs by the leader: |
|
Converted to discussion - we do not plan any new releases with any fixes anymore for 0.45. @ppatierno any idea what the problem might be? You know probably most abotu the migration. |
|
Any news on this? I cannot update to 1.0.0 if this blocks the migration to kraft. My cluster is now in a weird state and I hope it does not break production. |
|
Hi @sbildl, to me I'm not sure if you're following the right migration steps. Firstly, you must have a cluster that is already using a KafkaNodePool for the brokers before starting migration. So follow the steps in the docs to do that before starting migration to KRaft. Secondly, you stated that you set |
|
Hi @katheris, after my vacation, I am going to try it out and let you know if the problem was solved. Thanks for your help! |
Uh oh!
There was an error while loading. Please reload this page.
Bug Description
Zookeeper to KRaft migration in Operator 0.45.2 fails all the time.
Steps to reproduce
My Kafka
Expected behavior
Migration to KRaft works
Strimzi version
strimzi-kafka-operator-0.45.2
Kubernetes version
v1.36.1+k3s1
Installation method
Helm
Infrastructure
K3S Cluster
Configuration files and logs
Logs:
Additional context
I retried about ten times, nothing worked.
All reactions