Repository navigation
Use secureClientPort instead of clientPort #480
Description
Activity
Good news, ZOOKEEPER-4276 was fixed and will be released in
3.10.0🥳As ZK 3.10.0 is not released yet (and we do not know when/if it will) the scope of this is to see if the patch applies on 3.9.x
Reading the comments I doubt this will be the case. Please spend at moste one day on trying to get the patch to apply and if that doesn't work raise it for discussion and a decision on how to continue.
- moved this from Selected for Development to In Progress in Stackable End-to-End Coordination
on Dec 4, 2025
Currently for TLS and authentication we use the
clientPortinstead ofsecureClientPortdue to a bug in ZooKeeper (https://issues.apache.org/jira/browse/ZOOKEEPER-4276).Once this is fixed and we should switch from
clientPorttosecureClientPortand 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 #479.
This is currently blocked by stackabletech/tokio-zookeeper#57
The tokio-zookeeper client currently does not support TLS communication and therefore the operator can not manage znodes etc.
Tasks