-
Notifications
You must be signed in to change notification settings - Fork 734
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to access kafka brokers externally after using LoadBalancer #209
Comments
I've never seen these errors. There are other ways, to be found in various issues. For example #187 comes to mind. |
@solsson I tried changing |
This is a complicated topic and success factors depend a lot on your particular cluster setup. You'll have to dive into the reported errors. |
I am not sure why I am getting an |
There's no magic here. The current init.sh script in the applied config map takes effect whenever you restart a kafka pod. |
@solsson NVM, got the external access working with NodePorts and modifying security groups. Thanks for the help, closing the issue. |
Hi,
I tried exposing the individual Kafka brokers with NodePort and using LoadBalancer as well which created load balancers for each broker. But I am still not able to access them from outside.
Here's what I am seeing in logs:
Also, is there any other way to expose individual Kafka brokers externally without a need to create a load balancer for each of the brokers?
The text was updated successfully, but these errors were encountered: