Open akshaysolank opened 1 year ago
Hello @migruiz4 could you please assist me on it
Bitnami has different charts. Are you sure this is the correct repo for you to be posting in?
Otherwise, please note #638
I apologize for my mistake, @OneCricketeer. It appears that I posted the previous message on the wrong chat or thread.
Feel free to close this issue
Description: I am facing an issue with the deployment of a Kafka pod in Cluster A and its communication with microservices in Cluster B using a LoadBalancer (LB) defined for different brokers. Here are the details of the problem:
Cluster Configuration:
Cluster A: Contains the Kafka pod. Cluster B: Contains various microservices that need to communicate with the Kafka pod in Cluster A. Issue Description:
In Cluster B, we have defined the same Kafka LB for different brokers, and it works perfectly fine when microservices within Cluster A communicate with the Kafka pod. Problematic Behavior:
The issue arises when microservices in Cluster B try to communicate with the Kafka pod in Cluster A. We observe the following warning message in the Kafka logs:
Problem Details:
The error message indicates that the Kafka pod in Cluster A is unable to resolve the address kafka-2.kafka-headless.kafka-pod.svc.cluster.local:9092 when attempting to connect from Cluster B. This issue is causing communication problems between the microservices in Cluster B and the Kafka pod in Cluster A. Expected Outcome:
We expect the Kafka pod in Cluster A to successfully resolve the address and establish communication with microservices in Cluster B via the defined LoadBalancer.