-
Hi, because of special Network Requirements (using istio-cni and therefore we don't have network connectivity in init-containers at all) the kafka-init Container of the Kafka-Brokers isn't capable of doing the GET Kubernetes-API-Request for Node to generate the Rack ID. Because of other reasons, we are doing Kafka-Broker Pod AntiAffinity on our own and therefore we don't need the kafka-init Container to establish Rack Awareness. I reviewed the Strimzi Code and saw that there are several According to the Strimzi Documentation, the rack configuration is configured accordingly: https://github.com/strimzi/strimzi-kafka-operator/blob/main/documentation/api/io.strimzi.api.kafka.model.common.Rack.adoc -> but I didn't found a way to influence the resulting behaviour at all or found any hint in the source-code which CRD-Element I have to trigger to disable this init container. I checked also the TopicOperator for a way to insert a So in the end, is there a supported way to disable the rack awareness feature and therefore the kafka-init Container? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
You can disable Rack awareness by removing it from the Kafka CR - you had to enable it there in the first place. However, you should keep in mind that:
|
Beta Was this translation helpful? Give feedback.
You can disable Rack awareness by removing it from the Kafka CR - you had to enable it there in the first place. However, you should keep in mind that: