-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zookeeper SSL Failures When Certificate Is Rolled #359
Comments
I have the same issue. And zookeeper keeps failing with the below errors
|
I think the issue here is that although the Pulsar Helm Chart sets the The other Pulsar components (e.g. the bookie) solve this by having code inside them that watches the files under |
I am encountering the same issue with version 3.3.0 of the helm chart. The Pulsar Pods threw SSL-Exception( "notAfter: 15.04.2024"). Restarting the pods solved the issue. |
Restarting zookeeper did not fix the error: ` Caused by: java.security.cert.CertificateExpiredException: NotAfter: Tue Oct 01 17:19:15 UTC 2024
|
Another issue report: #524 |
Describe the bug
Zookeeper doesn't handle SSL certificate rolling gracefully. Specifically, if a certificate is rolled Zookeeper will continue to use the old, expired cert until it is restarted, which can lead to an outage as other components will be unable to communicate with it.
I'm not sure if this is an issue with the Pulsar Helm chart, or with Pulsar itself. If the latter, please let me know and I'll raise the issue there.
To Reproduce
Steps to reproduce the behavior:
The following is valid for Pulsar 2.92 using Helm chart 2.92
Expected behavior
Pulsar should continue to operate normally when a certificate is rolled
The text was updated successfully, but these errors were encountered: