stackabletech / stackabletech/zookeeper-operator
Make ZK clusterrole configurable
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 37
- Forks
- 11
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 10
Description
Currently this is hard-coded in the operator, which prevents us from deploying multiple instances of the chart into the same cluster, or using an alternate Helm release name to avoid conflicts.
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 locating the operator code that hard-codes the ZK ClusterRole and the Helm chart templates or values controlling the release name. Verify the change by deploying multiple chart instances, or an alternate Helm release name, in one cluster without ClusterRole conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, rust
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100