-
Notifications
You must be signed in to change notification settings - Fork 199
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
Allow exposing custom ports for kafka brokers #897
Comments
Hi @david-simon thanks for using koperator! This seems like a good first issue so maybe you could contribute this to the project? Also, could you think of some other scenarios where you think this could be useful for others as well? |
Hi @hi-im-aren I'll get back to you with some more use cases if I can |
Resolved in #898 |
Is your feature request related to a problem? Please describe.
I have a custom kafka distribution that has an integrated metrics exporter service exposed as a HTTP service. I would like to have this port added to the container and the service specs.
Describe the solution you'd like to see
I would like to have a new field added to the CRD (probably with the corev1.ContainerPort type) that will be used to create the kafka containers and services
Describe alternatives you've considered
I tried adding an additional container that would proxy requests to the metrics api but then I have to also create a new service for each broker that exposes this port. This is not ideal since then I have to monitor the number of kafka brokers and adjust the services accordingly.
The text was updated successfully, but these errors were encountered: