stackabletech / stackabletech/zookeeper-operator
ZNode discovery config only contains cluster-internal address, even when using listenerClass: external-unstable
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 37
- Forks
- 11
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 10
Description
Affected Stackable version
nightly (approaching 25.3)
Affected Apache ZooKeeper version
irrelevant
Current and expected behavior
When configuring external access I expect ZookeeperZnodes to behave the same as the main stacklet. Instead, their generated configmaps still only contain the cluster-internal address.
Possible solution
This should fall out naturally from Listenerification.
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
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
No files or tests are named. Start by tracing how ZookeeperZnodes generate their ConfigMaps and how Listenerification handles listenerClass: external-unstable; done means the generated ZNode configuration includes the external address as the main stacklet does.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100