apache / apache/pulsar-helm-chart

Deploy apache pulsar with external zookeeper

Open
#566 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
240
Forks
260
Avg merge
4h 12m
Merged PRs (30d)
1

Description

Hi All,

I have a zookeeper instance configured in a different namespace. I want to deploy the apache pulsar and use the zookeeper instance that I have in the other namespace.

In the values.yaml file i see an option to disable zookeeper. When I disable that, zookeeper instance is not created.

I also provided externalZookeeperServerList with my external zookeeper endpoints.

Now I notice that externalZookeeperServerList is used when zookeeper component is enabled. So, my zookeeper endpoints are not use by the helm chart and bookie and broker are always trying to connect to 127.0.0.1:2181.

Is there a way to configure pulsar to use external zookeeper instead.

Thanks,
Robert

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with values.yaml and the externalZookeeperServerList setting. Trace how disabling the Zookeeper component affects the bookie and broker configuration, focusing on the reported fallback to 127.0.0.1:2181. Done means the Helm chart uses the supplied external endpoints when the bundled Zookeeper is disabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
devops, distributed-systems
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.