Strimzi
-
|
Describe the bug I need to install this component multiple times on the same cluster, within different namespaces. Kafka Connect clusters have different names to avoid conflicts so I would expect cluster-operator to configure plugins only on the target cluster. However it seems that cluster operator firstly applies KafkaConnector from one namespace to both cluster, than does the same with ones from the other. It continues looping between the resources in the different namespaces and applies configs to both of them. You can look at logs for cluster-operator for insights: Below I will share the resources created on Kubernetes: ClusterOperator-namespace3.txt It seems that cluster-operator searches for CRD resources and applies all of them to all namespaces, without discriminating on the cluster name. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
I'm not entirely sure how exactly you run things. Connectors run on top of the Connect cluster, not the other way around as you seem to suggest. But maybe the problem is with this statement which is not true: |
Beta Was this translation helpful? Give feedback.
-
|
Hi @scholzj, I missed that paragraph in the official documentation. I tried it and it worked like a charm. |
Beta Was this translation helpful? Give feedback.
I'm not entirely sure how exactly you run things. Connectors run on top of the Connect cluster, not the other way around as you seem to suggest.
But maybe the problem is with this statement which is not true:
Kafka Connect clusters have different names to avoid conflicts so I would expect cluster-operator to configure plugins only on the target cluster.. This is a bit more complicated than this. The the Connect clusters connect all to the same Kafka clusters, you need to also configure the internal topics used by Connect. Otherwise they would act as one big Connect cluster. Check the docs for the details: https://strimzi.io/docs/operators/latest/full/deploying.html#con-kafka-connect-multi…