Connectivity or Communication between between Zeebe Gateway and Zeebe Broker

Hi Team,
We are using camunda8 self managed platfom. We have deployed camunda pods in Openshift cluster. We have our springboot application with zeebe client and zeebeGateway deployed on cluster A and camunda enviornment setup - zeebe , keycloak, identity, elastic serach, operated, tasklist, optimize in cluster B. We are trying to establish connectivity between zeebe Gateway(ClusterA) and Zeebe broker (Cluster B). Can this be achieved using HTTP ?

Also I wanted to know if zeebe Client and Zeebe gateway can only connect within same cluster using gRPC ?

Hi @ShilpaN.Chalke,

maybe this is possible, but it sounds weird.

Usually a Camunda 8 cluster consists of Zeebe brokers and gateway(s), Operate, Tasklist, Optimize, Identity, Keycloak and Elasticsearch.

If you include the worker app in the cluster, the network configuration of the worker will become easier as it is part of the same virtual network created by Openshift.

But if you choose SaaS, the worker is always running outside the Camunda 8 cluster. This is possible with Self-Managed as well, and you have to take care about the communication channel between gateway and worker regarding secure network traffic.

You will find more documentation about configuring the Worker - Gateway communication than the Gateway - Broker communication.

Hope this helps, Ingo

Hi @Ingo_Richtsmeier ,
We are using self managed openshift platform
For us Ideal scenario is to have our Application with zeeClient @ cluster A and All Camunda Pods - Zeebee , GateWay, Identity, Operate etc. @cluster B . But then we are not sure if our ZeebeClient on Cluster A can connect to Cluster B Zeebee Broker via gRPC 26500 ?
Is gRPC communication possible between 2 different clusters?

“If you include the worker app in the cluster, the network configuration of the worker will become easier as it is part of the same virtual network created by Openshift” - Our current implementation is similar to this approach.
But we are looking to separate the worker/ client application and the actual Zeebe in 2 different clusters and have mutiple applications use same Zeebe cluster.