'Kafka Headless Service Issue

Headless service does not bind to new IPs. A pod restart is required. When both zookeepers and brokers restarted at same time brokers are not able to connect with zookeeper using headless service.

Port details : Zookeeper headless service - 2888/TCP,3888/TCP

Port: server  2888/TCP
TargetPort: 2888/TCP
Endpoints:         10.233.109.66:2888,10.233.76.221:2888,10.233.82.178:2888
Port: leader-election  3888/TCP
TargetPort: 3888/TCP
Endpoints:         10.233.109.66:3888,10.233.76.221:3888,10.233.82.178:3888

Kafka headless service - 9092/TCP

Endpoints:         10.233.109.37:9092,10.233.76.141:9092,10.233.82.155:9092

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source

'Kafka Headless Service Issue

Sources

Related Questions