KIP-1312 is going to add a mechanism to unregister controllers as it's already available for brokers (which is already used within the cluster operator).
The KIP is probably going to land into Apache Kafka 4.4 and we should leverage the new feature to avoid scenarios like the one discussed here https://github.com/orgs/strimzi/discussions/11147
Without the support for dynamic quorum (yet) and controllers scaling, it seems more users fall in this issue which should not happen anymore if the cluster operator would be able to unregister a controller, from within the static quorum, when it's shut down.
To follow the Kafka implementation for such KIP, here is the KAFKA-20395 JIRA.
KIP-1312 is going to add a mechanism to unregister controllers as it's already available for brokers (which is already used within the cluster operator).
The KIP is probably going to land into Apache Kafka 4.4 and we should leverage the new feature to avoid scenarios like the one discussed here https://github.com/orgs/strimzi/discussions/11147
Without the support for dynamic quorum (yet) and controllers scaling, it seems more users fall in this issue which should not happen anymore if the cluster operator would be able to unregister a controller, from within the static quorum, when it's shut down.
To follow the Kafka implementation for such KIP, here is the KAFKA-20395 JIRA.