-
Hi. Another question for you today, on the possibility to deploy 2 Kafka (Strimzi) clusters on the same namespace. We always have this periodic error (only on the second cluster entity-operator):
Despite both cluster has created the named topic: It's like they can't share the same default topics. Do we have something to specify to avoid this ? |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 9 replies
-
When you run multiple topic and user operators with different Kafka clusters in the same namespace, it will have limitations to what topics and users can exist. Because Kubernetes can have only one KafkaTopic or KafkaUser resource with a given name. So in general, you should run it in different namespaces (or disable the entity operator for one cluster). |
Beta Was this translation helpful? Give feedback.
-
Hi Jakub, it's me again. I've just found this part of your documentation: https://strimzi.io/docs/operators/latest/using.html#overview-concepts-topic-operator-str So, the ClusterOperator is only here to manage K8S resources (KafkaTopic and KafkaUser). So what will be the problem (if any ?) if we run multiple Kafka clusters on the same namespace ? Thanks. |
Beta Was this translation helpful? Give feedback.
-
Hi @scholzj! My case is also that deployed more than one kafka cluster in one namespace. As you suggested "Because Kubernetes can have only one KafkaTopic or KafkaUser resource with a given name. So in general, you should run it in different namespaces (or disable the entity operator for one cluster)." So I only enabled entity operator for one kafka cluster and disabled it for others in the namespace. Then I created one KafkaUser resource which label to the kafka cluster which enabled entity operator. With this case, I want to use the same username for the kafka clusters in the namespace. No matter one same user or multiple users with same name. Could you help point me a feasible solution? Thanks a lot! BR |
Beta Was this translation helpful? Give feedback.
-
@scholzj Yes, I understand the recommendation is about best practice. However we have limitation. If there is no good way to get help with KafkaUser under my case, I have to go to kafka API. Thanks for your kind help. Meanwhile, I am still curious about the description in document. Looking forward to your answer @PaulRMellor :) |
Beta Was this translation helpful? Give feedback.
When you run multiple topic and user operators with different Kafka clusters in the same namespace, it will have limitations to what topics and users can exist. Because Kubernetes can have only one KafkaTopic or KafkaUser resource with a given name. So in general, you should run it in different namespaces (or disable the entity operator for one cluster).