You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Requirement: Giving access to Kafka brokers from within a k8s cluster.
Currently, only the external cluster IP is per default advertised by brokers. For my particular setup, this IP:port address isn't and shouldn't be accessible, not from inside or outside of the cluster.
When trying to set the advertised.listeners property of Kafka through KafkaCluster, it is not picked up by the broker configuration, see configuration below. This results in Kafka being effectively not usable in this particular scenario.
yet, the broker itself still does it's own override using the node port (CLIENT://$NODE:$(cat /stackable/tmp/kafka_nodeport)), not preferring the intended override:
Affected version
docker.stackable.tech/stackable/kafka-operator:23.1.0
Current and expected behavior
Requirement: Giving access to Kafka brokers from within a k8s cluster.
Currently, only the external cluster IP is per default advertised by brokers. For my particular setup, this IP:port address isn't and shouldn't be accessible, not from inside or outside of the cluster.
When trying to set the
advertised.listeners
property of Kafka throughKafkaCluster
, it is not picked up by the broker configuration, see configuration below. This results in Kafka being effectively not usable in this particular scenario.kcat shows that brokers still advertise the original external ip regardless of the override.
the brokers configmap contains the override:
yet, the broker itself still does it's own override using the node port (
CLIENT://$NODE:$(cat /stackable/tmp/kafka_nodeport)
), not preferring the intended override:Possible solution
No response
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
The text was updated successfully, but these errors were encountered: