Zookeeper TLS Support
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 818
- Avg merge
- 1h 14m
- Merged PRs (30d)
- 1
Description
I was investigating this project at the end of 2018 and found an issue which had some example code to add TLS support for the Zookeeper connection. However, I cannot seem to find it anymore and was wondering if TLS support had indeed been added to Burrow as of 1.1.0?
My specific use-case is that I am running Kafka with Strimzi, which by default includes Stunnel sidecars on all components in the cluster. This means all connectivity is secured via TLS - as such, if we want Burrow to connect to the Zookeepers, they need to do so in an authenticated fashion using a certificate.
Otherwise I may be able to write this feature myself and issue a pull request.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by determining whether Burrow 1.1.0 already supports authenticated TLS connections to Zookeeper, then inspect the existing Zookeeper connection path. Confirm the required certificate configuration for Kafka deployments using Strimzi and Stunnel, and define done as a working TLS connection with suitable validation or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kafka
- Domain
- distributed-systems, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100