[Bug]: Renew CA certificates and private keys with your own (Before Expiry renewal) failing #9045
Replies: 3 comments 2 replies
-
This is not how you are supposed to renew the certificate. You seem to generate a brand new private and public key and replace just the public key. You should upgrade to the latest version and follow the documentation for the renewal. |
Beta Was this translation helpful? Give feedback.
-
Kafka Cluster and client certs are not getting renewed as We performed the following steps now : I) Pausing reconciliation restarting the deployment |
Beta Was this translation helpful? Give feedback.
-
Can you provide me the openssl commands for renewing the certs from the old key . The documentation dosen.t help me to get the commands for doing this . openssl verify -CAfile ca.crt crt_from_zookeper.crt |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Bug Description
I created my own certificate as below and updated the cluster-cert as mentioned in Strimzi documents
I deleted the old cluster-ca-cert and recreated the cert as above and restarted the zookeper pod and i see the below in
LOG: ---------------------------------
Setected Zookeeper ID 3
But it fails to restart and on the logs it shows the following
Preparing truststore
Adding /opt/kafka/cluster-ca-certs/ca.crt to truststore /tmp/zookeeper/cluster.truststore.p12 with alias ca
Certificate was added to keystore
Preparing truststore is complete
Looking for the right CA
No CA found. Thus exiting.
When i replace the cluster-ca-cert to the old cert the pod again runs fine .
Please help , I am not sure if am missing on something
Steps to reproduce
delete the old cert
I deleted the old cluster-ca-cert and recreated the cert as above and restarted the zookeper pod and i see the below in
LOG: ---------------------------------
Setected Zookeeper ID 3
Expected behavior
Zookeper should take the newly generated certificate
Strimzi version
0.27
Kubernetes version
1.24
Installation method
helm insatll
Infrastructure
GKE
Configuration files and logs
Setected Zookeeper ID 3
But it fails to restart and on the logs it shows the following
Preparing truststore
Adding /opt/kafka/cluster-ca-certs/ca.crt to truststore /tmp/zookeeper/cluster.truststore.p12 with alias ca
Certificate was added to keystore
Preparing truststore is complete
Looking for the right CA
No CA found. Thus exiting.
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions