Reminder: we need to decide about the developement of Apache Pulsar Helm chart. Please reply to the email or review https://github.com/apache/pulsar-helm-chart/pull/190 . That PR is blocked since a decision must be made whether it's fine to make the change, although there's a known issue in Zookeeper when TLS is enabled. The issue is ZOOKEEPER-3988 / https://github.com/apache/pulsar/issues/11070 . The bug currently only impacts TLS since the change https://github.com/apache/pulsar-helm-chart/pull/180 switched to use NIOServerCnxnFactory for Zookeeper. NIOServerCnxnFactory doesn't support TLS and the impacted NettyServerCnxnFactory must be used for TLS.
How do we handle the decision? Can we proceed in merging https://github.com/apache/pulsar-helm-chart/pull/190 regardless of the known issue? BR, Lari On Mon, Jan 3, 2022 at 4:39 PM Lari Hotari <lhot...@apache.org> wrote: > Hi all, > > There's an upcoming change in the Apache Pulsar Helm chart to finally > switch to Pulsar 2.8.x, more specifically to Apache Pulsar version 2.8.2 . > The latest Apache Pulsar Helm Chart release uses the Apache Pulsar 2.7.4 > image. > > The pull request to switch to Apache Pulsar image version 2.8.2 is current > in review: > https://github.com/apache/pulsar-helm-chart/pull/190 > > There's a known issue that Zookeeper TLS isn't stable because of > https://issues.apache.org/jira/browse/ZOOKEEPER-3988 (also reported in > apache/pulsar as https://github.com/apache/pulsar/issues/11070) . > The fix https://github.com/apache/zookeeper/pull/1770 is planned for > Zookeeper 3.7.1 version. > There's a workaround in the Apache Pulsar Helm chart when TLS isn't > enabled for Zookeeper. That was added by > https://github.com/apache/pulsar-helm-chart/pull/180 . > However, the workaround cannot be applied when TLS is enabled for > Zookeeper. > > Should we postpone switching to Apache Pulsar 2.8.2 in the Helm chart > until there's a fix for ZOOKEEPER-3988 / > https://github.com/apache/pulsar/issues/11070 ? > > BR, > Lari >
