-
Notifications
You must be signed in to change notification settings - Fork 79
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
NodePort allocate failed since conflict occur when multiple Kafka instances with external NodePort services expose #266
Comments
Version information: KUDO Version Operator version App version |
@walk1ng we don't recommend using nodeports and this shouldn't be the first choice to run KUDO Kafka in production https://github.com/kudobuilder/operators/blob/master/repository/kafka/docs/latest/external-access.md#nodeports but as you said you can specify the |
Hi zmalik, thanks for your quick response. |
@walk1ng right now we haven't implemented that. Because that would mean that for clients to connect to a newly created Kafka cluster they would need to know the dynamic nodeport that just got assigned to the services. And that would be different for each Kafka broker. |
Hi teams,
When I use Kafka operator to install multiple Kafka instances in the same k8s cluster and all Kafka with external NodePort type services exposed, the nodePorts maybe conflicted assignment here.
e.g.
that's the conflict assignment.
Check the plan status of instance, you can get the error similar as "Invalid value: 30902: provided port is already allocated".
I know there is a parameter "EXTERNAL_NODE_PORT" to specify the port, but it's a starting value and operator will count the other ports according to brokers count, it also have the chance to get the used ports then install Kafka failed.
Cloud you please help. Thanks!
The text was updated successfully, but these errors were encountered: