Replies: 1 comment
-
That is not supported and will not work currently. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello.
I deploy Kafka Connect using Strimzi with the same configuration across more than two K8S clusters.
I want to logically use these multiple K8S clusters as a single Kafka Connect cluster by using the same group.id and config topics. (distributed-mode)
However, when the Kafka Connect cluster is configured in this way, workers cannot find the leader worker, making the REST API unusable. I suspect this is because the rest.advertised.host.name is set to the worker's name, which prevents communication to workers in other K8S clusters. If, by chance, API requests reach the K8S cluster where the leader worker is located, the API functions properly. However, even in this situation, communication between workers fails, preventing task creation.
Therefore, I thought that changing the rest.advertised.host.name to the host IP and exposing it via nodeport might solve the issue of enabling communication between worker nodes located in different K8S clusters.
However, I found that in the Strimzi configuration, the rest.* options are rejected.
Question
Does Strimzi not support using multiple K8S clusters as a single Kafka Connect cluster in this manner?
How can I use multiple K8S clusters as a single Kafka Connect cluster?
My Config
Below is my Strimzi K8S config. It is being deployed identically on two K8S clusters. (excluding the ingress-related configurations)
log
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions