d80tb7 opened a new issue, #359: URL: https://github.com/apache/pulsar-helm-chart/issues/359
**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 1. Deploy Pulsar into a K8s cluster using the Helm chart with tls enabled for zookeeper and certs managed by certmanager 2. Wait for the certificate to be rolled 3. See connections to zookeeper fail with "io.netty.handler.codec.DecoderException: javax.net.ssl.SSLHandshakeException: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed...Caused by java.security.cert.CertificateExpiredException " 4. Restart Pulsar Pods and see that errors go away **Expected behavior** Pulsar should continue to operate normally when a certificate is rolled -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
