ptemarvelde opened a new issue, #706: URL: https://github.com/apache/pulsar-helm-chart/issues/706
**Describe the bug** Bookkeeper-cluster-initialize does not use TLS port when TLS is enabled. **To Reproduce** Steps to reproduce the behavior: 1. Deploy the Pulsar Helm chart with TLS enabled (e.g., `tls.zookeeper.enabled=true`). 2. Wait for the ZooKeeper cluster to become ready. 3. Check the logs or status of the `bookkeeper-cluster-initialize` job. 4. See error: The initialization job fails to connect to ZooKeeper because it is attempting to use the standard non-TLS port instead of the secure TLS port. ``` KeeperErrorCode = ConnectionLoss for <metadataPrefix> ``` **Expected behavior** The `bookkeeper-cluster-initialize` job should automatically detect that TLS is enabled and connect to ZooKeeper using the correct secure TLS port. **Additional context** The root cause is in `charts/pulsar/templates/bookkeeper-cluster-initialize.yaml` at [line 117](https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/bookkeeper-cluster-initialize.yaml#L117). It does not use the correct server connection string that accounts for TLS. It should be updated to use the `pulsar.zookeeper.connect` template defined in [`_zookeeper.tpl` at line 37](https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/_zookeeper.tpl#L37), which properly handles the logic for appending the TLS port when it is enabled. -- 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]
