Upgrading Kafka from 3.8.0 to 3.9.0 fails during creation of custom cert keystore in broker #11446
Replies: 2 comments 3 replies
-
This is wrong:
You have to use image for the Kafka version and Strimzi version you use. Not |
Beta Was this translation helpful? Give feedback.
2 replies
-
Sorry, not a Strimzi issue. The certificates were wrongly configured during update. I was automating through Python that broke the certificates during upgrades. |
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.
-
I'm upgrading Kafka from 3.8.0 to 3.9.0 and noticed that the broker fails to create the keystore for the custom listener with custom certs.From the pod description, the volume is mounted from the secret
tls-kafka-external
and the secret has the keytls.key
. It is an unencrypted private key that worked with the previous version. The controller pods were upgraded fine but the broker pods fail with the following log statements -The external listener is configured as follows -
The cluster was working with version 3.8.0 but fails when upgraded to 3.9.0. The cluster works if started with 3.9.0 with the exact same configuration/certs but not during upgrade.
The cluster uses a custom image that adds tiered storage support. The base image version is set appropriately. The Dockerfile for reference -
Strimzi version - 0.45.0
Beta Was this translation helpful? Give feedback.
All reactions