[
https://issues.apache.org/jira/browse/KAFKA-19021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104504#comment-18104504
]
Omnia Ibrahim commented on KAFKA-19021:
---------------------------------------
Moving to 4.5 as we are now in 4.4.0 code freeze
> Broker should not be allowed to be promoted to controller
> ---------------------------------------------------------
>
> Key: KAFKA-19021
> URL: https://issues.apache.org/jira/browse/KAFKA-19021
> Project: Kafka
> Issue Type: Sub-task
> Components: kraft
> Reporter: José Armando García Sancio
> Assignee: José Armando García Sancio
> Priority: Major
> Fix For: 4.4.0
>
>
> It is possible for the user to add broker as a controller by using
> "kafka-metadata-quorum add-controller". This can be fixed by having the
> controller check the set of RPC exposed in the ApiVersion response.
> The leader already makes a call to ApiVersion to check the kraft.version of
> the new controller. The leader should extend this check to make sure that the
> node also supports all of the KRaft RPCs. That includes Vote, FetchSnapshot,
> BeginQuorum, EndQuorum, etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
