stackabletech / stackabletech/zookeeper-operator
Use secureClientPort instead of clientPort
@maltesander is already working on this.
Since Dec 3, 2025.
- Dominant language
- Rust
- Stars
- 37
- Forks
- 11
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 10
Description
Currently for TLS and authentication we use the clientPort instead of secureClientPort due to a bug in ZooKeeper (https://issues.apache.org/jira/browse/ZOOKEEPER-4276).
Once this is fixed and we should switch from clientPort to secureClientPort and remove the portUnification property (allows plaintext and secured communication via the same port).
The necessary steps are documented in the code (see rust/crd/src/lib.rs)
Since this does not work in versions 3.8.0 or lower, it will be a little more work to differentiate between zookeeper versions with and without that bug.
Relates to PR https://github.com/stackabletech/zookeeper-operator/pull/479.
This is currently blocked by https://github.com/stackabletech/tokio-zookeeper/issues/57
The tokio-zookeeper client currently does not support TLS communication and therefore the operator can not manage znodes etc.
Tasks
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.
Assessment
This issue has not been assessed yet.