Thanks for your prompt reply. Yeah it’s an On-Premise installation. I’m using Kubernetes Kind to create cluster. I found out that when I changed the option “–values x.yaml” into “-k kind_values.yaml” then it worked. Maybe it’s because I’m using kubernetes kind to create kubernetes cluster(I’m not sure but it worked).
Currently, we have 3 servers (let’s say 192.168.26.99, 192.168.26.100, 192.168.26.101), I want to setup Zeebe-cluster and distribute workload to 3 of them. Can you give me some suggestions or an example on how to config. I see in Helm-chart config https://github.com/zeebe-io/zeebe-helm-profiles/raw/master/zeebe-core-team.yaml, I only need to config the number of clusters then automatically 3 brokers are spawned,… I don’t know how to deal with traffic and communication when deploying them on different servers, the contact points or something else. We used to work with zeebe-cluster-docker-compose.yml for developing but now we want to deploy it for production environment. With zeebe docker-compose version, I used to try to deploy 3 zeebe brokers on 3 servers and routing contact points to each other but problems of communication, grpc, and raftserver were thrown and I think Helm chart with K8s will help us handle those. Can you show me how to setup the Zeebe-cluster correctly? I will need to build 3 nodes on 3 servers or something like that. As I have noted, I’m new to K8s and I’m learning more about it.