Kafka mTLS Client CA Secret Update Not Detected #12536
Replies: 2 comments 3 replies
-
|
Strimzi does not really know what and how you use in the |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
How can we configure multiple client CA certificates? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We have enabled mTLS using
type: custom, as referenced in issue #11052. However, we are encountering an issue during the renewal of the client CA certificate.When we update the certificate in the
custom-truststoresecret, the changes are not being reflected in the Kafka cluster. Under normal behavior, updating a secret should trigger a rolling update of the Kafka pods so that the new certificates are picked up. In this case, the pods are not restarting, and the updated configuration is not being applied.It is worth noting that updating the server/broker custom secret (configured under
brokerCertChain) is working as expected, and the pods are rolling correctly in that scenario. The issue appears to be specific to the client CA configuration defined under thesecrets:section.Could you please advise on the correct approach to ensure that updates to the client CA secret are detected and applied by Kafka? Additionally, is there any recommended workaround or configuration required to trigger a rolling update for such changes?
Beta Was this translation helpful? Give feedback.
All reactions