stackabletech / stackabletech/zookeeper-operator
Use secureClientPort instead of clientPort
@maltesander ci sta già lavorando.
Dal 3/12/2025.
- Lingua principale
- Rust
- Stelle
- 37
- Fork
- 11
- Merge medio
- 1g 8h
- PR unite (30g)
- 10
Descrizione
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
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Valutazione
Questa issue non è ancora stata valutata.