stackabletech / stackabletech/zookeeper-operator
Improvement: Emit warning when using multiple RoleGroups without a myidOffset
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 37
- Forks
- 11
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 10
Description
Context
The ZK operator uses the ordinal index of pods in the RoleGroup statefulsets to assign a myid to each replica. This approach leads to duplicate IDs when using more than one RoleGroup, als all indices are 0-based. To prevent ID collisions, a custom myidOffset needs to be specified, for which we wrote documentation.
Improvement
The operator doesn't do anything when there are multiple role-groups without an offset. The operator should at least emit a warning
Reference comment: https://github.com/stackabletech/zookeeper-operator/issues/546#issuecomment-1348056967
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 with the operator's RoleGroup reconciliation path and read the linked documentation on using multiple RoleGroups, followed by the reference comment from issue 546. Trace the handling of multiple groups without myidOffset and add coverage for the warning; done means this configuration emits a clear warning without an offset.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100