wuYin opened a new pull request #38: URL: https://github.com/apache/pulsar-helm-chart/pull/38
Fixes #<xyz> ### Motivation - Background: I have a physical zk cluster and want configure bookkeeper & broker & proxy to use it. - Try: I set [components.zookeeper](https://github.com/apache/pulsar-helm-chart/blob/8f9c1d126e5a92d4dbf62412687c9511cc306d99/charts/pulsar/values.yaml#L75) as false, and only found [pulsar.zookeeper.connect](https://github.com/apache/pulsar-helm-chart/blob/8f9c1d126e5a92d4dbf62412687c9511cc306d99/charts/pulsar/templates/_zookeeper.tpl#L11) to set my physical zk address. - Problem: The [wait-zookeeper-ready initContainer](https://github.com/apache/pulsar-helm-chart/blob/8f9c1d126e5a92d4dbf62412687c9511cc306d99/charts/pulsar/templates/bookkeeper-cluster-initialize.yaml#L33) in bookkeeper-cluster-initialize Job used spliced zk Service hosts to detect zk ready or not, other component init Job initContainer do the same thing. Actually, zk service are unreachable because I disabled zk component. - Effect: Deploy stage will be stucked in bookkeeper wait-zookeeper-ready container. ### Modifications - Add optional pulsar_metadata.userProvidedZookeepers config for this case, and make component's init Job use user zk to detect liveness, instead of spliced Service hosts. - Delete redundant image reference in bookkeeper init Job. ### Verifying this change - [ ] Make sure that the change passes the CI checks. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
