Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Optional Load Balancer (+ external IP) for bootstrap server when using type "loadbalancer"
See original GitHub issueIs your feature request related to a problem? Please describe.
When using type loadbalancer for a Kafka listener, n+1 Load Balancers are created in Kubernetes, n for the amount of brokers and 1 for the bootstrap server.
Describe the solution you’d like
The bootstrap server is only for convenience (as discussed here), which may not be always necessary. Providing a flag in the configuration for the loadbalancer type listener stating whether to provision a Load Balancer for the bootstrap server would be a nice addition.
Describe alternatives you’ve considered The only alternative now is to always provision a bootstrap Load Balancer service.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think the name will be a bit different depending on the listener name in the Kafka CR. But yes, the regular
test-kafka-01-kafka-bootstrapservice should be kept -> only thetest-kafka-01-kafka-external-bootstrapwould be basically not created if the user does not want to use it (the motivation is usually to save costs - thetest-kafka-01-kafka-external-bootstrapis convenient for configuring the clients, but strictly speaking not needed).@scholzj please assign this issue to me, I opened a PR for this issue. thanks!