[X] I've searched for an already existing issues here
[X] I'm running a supported version of the application which is listed here and the feature is not present there
Is your proposal related to a problem?
No response
Describe the feature you're interested in
For clusters running in KRaft mode, the describe cluster API currently returns any alive broker's ID as controller ID Link to code. I believe this was done because, before KIP-919, clients couldn’t directly communicate with controllers and had to connect through brokers, making the specific broker ID irrelevant. Given this, perhaps for KRaft clusters, it might be better not to display the active controller indicator (and the green tick in front of the broker ID) to avoid confusing users?
Alternatively, in addition to the broker list, it might be helpful to also display the controller list by calling the describe cluster API with EndpointType set to 2. Or perhaps this could be displayed as a single list, since some nodes may have both broker and controller roles. In this scenario, displaying the active controller would make sense.
Issue submitter TODO list
Is your proposal related to a problem?
No response
Describe the feature you're interested in
For clusters running in KRaft mode, the describe cluster API currently returns any alive broker's ID as controller ID Link to code. I believe this was done because, before KIP-919, clients couldn’t directly communicate with controllers and had to connect through brokers, making the specific broker ID irrelevant. Given this, perhaps for KRaft clusters, it might be better not to display the active controller indicator (and the green tick in front of the broker ID) to avoid confusing users?
Alternatively, in addition to the broker list, it might be helpful to also display the controller list by calling the describe cluster API with EndpointType set to 2. Or perhaps this could be displayed as a single list, since some nodes may have both broker and controller roles. In this scenario, displaying the active controller would make sense.
Describe alternatives you've considered
No response
Version you're running
1.0.0
Additional context
No response