Open marcelloromani opened 10 months ago
In my setup Cruise Control is running as a pod on an EKS cluster which resides in the same AWS Account as the MSK cluster.
I double checked the Pod Service Account -> IAM Role mapping and verified that the IAM Role has a Policy which allows all of the Kafka operations on the relevant MSK cluster.
Happy to provide more details about this if deemed useful.
I am using Cruise Control 2.5.99 with AWS MSK. I reached the point where Curise Control is able to connect to the Kafka brokers, but terminates with the following exception:
As the stacktrace indicates, that error message comes from: https://github.com/linkedin/cruise-control/blob/9ccbb9eeb497b23d9e98e76f7512abea908366af/cruise-control/src/main/java/com/linkedin/kafka/cruisecontrol/config/KafkaAdminTopicConfigProvider.java#L172
The
catch
statement simply swallows anyExecutionException
and replaces any useful error with the generic message "Failed to describe Kafka cluster configs."It would be useful if it instead logged the original exception or included it in the generic RunTimeException message.