Description
Bug Description
Hello,
the migration to KRaft is failing when Kafka is configured to use a Custom Authorizer.
Maybe it is just a lack in the documentation however, at some point the legacy Custom Authorizer is still used and when it tries to access Zookeeper, it fails.
So there is a point in the migration where we need to switch from the legacy Custom Authorizer to the KRaft-compatible Custom Authorizer.
We would need to understand how the migration should occur when we are using a Custom Authorizer.
Steps to reproduce
Follow the KRaft migration steps with a Custom Authorizer (that uses Zookeeper). At some point, the brokers will fail.
Expected behavior
Provide a documented way of migrating to KRaft when using a custom authorizer.
Strimzi version
0.45.0
Kubernetes version
Openshift 4.16.42
Installation method
Yaml files
Infrastructure
Azure
Configuration files and logs
strimzi-cluster-operator-app-56b4b8b6c6-xz8gz-strimzi-cluster-operator.log
bkxs30-kafka-0-kafka (1).log
bkxs30.yaml.txt
Additional context
No response