Yolean / kubernetes-kafka

Kafka cluster as Kubernetes StatefulSet, plain manifests and config
Apache License 2.0
1.83k stars 738 forks source link

Issue on external service (Kafka) #344

Open tittuvarghese opened 3 years ago

tittuvarghese commented 3 years ago

There is some issue with exposing the NodePort for outside access in Kafka. It's refusing the connection even though the service is up and running as per the logs.

[root@AWSB outside-services]# kubectl logs -n kafka kafka-1 2>&1 | grep 9094
        listeners = PLAINTEXT://:9092,OUTSIDE://:9094
        listeners = PLAINTEXT://:9092,OUTSIDE://:9094
[2021-04-30 10:01:12,968] INFO Awaiting socket connections on 0.0.0.0:9094. (kafka.network.Acceptor)
[2021-04-30 10:01:12,979] INFO [SocketServer brokerId=1] Created data-plane acceptor and processors for endpoint : EndPoint(null,9094,ListenerName(OUTSIDE),PLAINTEXT) (kafka.network.SocketServer)

[root@AWSB outside-services]# curl -v telnet://10.7.18.16:32400
* Rebuilt URL to: telnet://10.7.18.16:32400/
*   Trying 10.7.18.16...
* TCP_NODELAY set
* connect to 10.7.18.16 port 32400 failed: Connection refused
* Failed to connect to 10.7.18.16 port 32400: Connection refused
* Closing connection 0
curl: (7) Failed to connect to 10.7.18.16 port 32400: Connection refused

[root@AWSB outside-services]# kubectl get svc -n kafka | grep out
outside-0       NodePort    172.102.169.196   <none>        32400:32400/TCP     37m
[root@AWSB outside-services]#
solsson commented 3 years ago

Could #187 be related? It's quite possible that general purpose outside access must be outside the scope of this project. Obviously it's also possible that you've stumbled upon a regression. If you think so please state which branch or commit you applied from.