You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Gaurav Narula (Jira)" <ji...@apache.org> on 2026/08/12 15:20:00 UTC
[jira] [Comment Edited] (KAFKA-20931) Kraft network client doesn't handle certificate rotation
[ https://issues.apache.org/jira/browse/KAFKA-20931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18104101#comment-18104101 ]
Gaurav Narula edited comment on KAFKA-20931 at 8/12/26 3:19 PM:
----------------------------------------------------------------
[~christo_lolov] I believe there's an open PR for this that you might want to look at https://github.com/apache/kafka/pull/21333
Edit: Seems duplicate of KAFKA-20025
was (Author: gnarula):
[~christo_lolov] I believe there's an open PR for this that you might want to look at https://github.com/apache/kafka/pull/21333
> Kraft network client doesn't handle certificate rotation
> --------------------------------------------------------
>
> Key: KAFKA-20931
> URL: https://issues.apache.org/jira/browse/KAFKA-20931
> Project: Kafka
> Issue Type: Bug
> Components: core
> Reporter: Christo Lolov
> Priority: Major
>
> Kafka supports "online" certificate rotations via dynamic configurations for key and trust stores. In cases such as NodeToControllerChannelManager the channel builder registers itself as a reconfigurable so that it gets updates. However, KafkaRaftManager's channel builder does not do this as part of creating the network client. In the event of a certificate expiry this leads to the need to restart the Kafka process so that the new certificates are picked up.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)