-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Add ability to connect to bookkeeper using tls #3376
Comments
@bputt just try to clarify your requirement here: are you looking for "connecting your pulsar clients to brokers via TLS" or "connecting your pulsar broker to bookies via TLS"? |
@sijie "connecting your pulsar broker to bookies via TLS" |
@bputt gotcha, thank you for clarification. |
👍 |
This functionality would be very useful for running a secure cluster and allowing a separate Pulsar functions cluster to also communicate with BK. Super interested in having that capability. |
For TLS, It need these configs: We need add and support these config in BookKeeperClientFactoryImpl, which is similar to bk client config in it. |
Any update on this issue? Is there an ETA for this? |
@david-streamlio Is that you are looking for? |
Yes, thank you!! |
Is your feature request related to a problem? Please describe.
I have a bookkeeper cluster that has TLS enabled and need pulsar clients to communicate to my cluster using tls
Describe the solution you'd like
The ability to specify tls settings for my broker to connect to bookkeeper
Describe alternatives you've considered
Using stunnel + iptables to redirect
The text was updated successfully, but these errors were encountered: