GitHub user Khemendra-Bhardwaj added a comment to the discussion: How to set up Broker config and other configs like bookie etc
> > Should I add the key : > > PULSAR_PREFIX_loadBalancerSheddingEnabled= true > > to charts/pulsar/templates/broker-configmap.yaml in pulsar helm repo ? > > No. For Helm charts, you usually pass a value.yaml file to configure the > options. In your values.yaml, you could do this: > > ```yaml > broker: > configData: > loadBalancerSheddingEnabled: "true" > ``` > > You don't need to have `PULSAR_PREFIX_` as the prefix for the key since > `loadBalancerSheddingEnabled` exists in the default `conf/broker.conf` file > in the docker image. Hey, I think the issue is best suited to ask here I need some suggestions regarding my current setup. I’m running an AWS EKS cluster in the ap-south-1 region with three EC2 instances across different availability zones (1a, 1b, and 1c). Each node hosts a single instance of Bookkeeper, Zookeeper, Broker, and Proxy. I plan to use AWS EBS for persistent volume provisioning. Specifically, for each node, I will have one AWS EBS volume in the corresponding zone to store Zookeeper and Bookkeeper data (journal and ledgers). We’re deploying Pulsar using a Helm chart. Could you provide guidance on how to approach this setup for static volume provisioning , Iike specifying which files and changes are needed. ( Do I need to manually create PV and PVC for each pod of zookeeper and bookeeper and label it to nodes , and specify the mounted path, ? ) GitHub link: https://github.com/apache/pulsar/discussions/19276#discussioncomment-10474050 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
