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
I'm trying to set-up kafka-proxy in Kubernetes to connect to Kafka outside Kubernetes. I am able to connect and use Kafka as expected (I'm using edenhill's kcat for this), but after roughly 2 minutes the proxy just closes the connection to the broker without further explanation.
This doesn't happen when running the proxy in docker, only in Kubernetes, which suggests a problem when dealing with Kubernetes networking. Does anyone know what is happening or why? Thanks in advance!
Bellow are my manifests for Deployment and Service, and the logs at debug level. The BROKER-IP used is censored, but it does work and resolve into a public IP where the broker is.
time="2022-09-20T18:52:06Z" level=info msg="Starting kafka-proxy version v0.3.1"
time="2022-09-20T18:52:06Z" level=info msg="Bootstrap server BROKER-IP:9095 advertised as 10.11.19.221:30001"
time="2022-09-20T18:52:06Z" level=info msg="Listening on 0.0.0.0:3000 ([::]:3000) for remote BROKER-IP::9095"
time="2022-09-20T18:52:06Z" level=info msg="Ready for new connections"
time="2022-09-20T18:53:35Z" level=info msg="Closing connections"
time="2022-09-20T18:53:35Z" level=info msg="Proxy is stopped"
time="2022-09-20T18:53:35Z" level=info msg="Exit received signal terminated"
The text was updated successfully, but these errors were encountered:
Hello!
I'm trying to set-up kafka-proxy in Kubernetes to connect to Kafka outside Kubernetes. I am able to connect and use Kafka as expected (I'm using edenhill's kcat for this), but after roughly 2 minutes the proxy just closes the connection to the broker without further explanation.
This doesn't happen when running the proxy in docker, only in Kubernetes, which suggests a problem when dealing with Kubernetes networking. Does anyone know what is happening or why? Thanks in advance!
Bellow are my manifests for Deployment and Service, and the logs at debug level. The BROKER-IP used is censored, but it does work and resolve into a public IP where the broker is.
Deployment
NodePort Service
Error message
The text was updated successfully, but these errors were encountered: