Altinity / Altinity/clickhouse-operator
feature: replicaGroup
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
Ability to define groups of replicas in easy way, so they can share specific podTemplate:
For example replicas 1 & 2 should use regular ec2 instances and replicas 3+ should use ephemeral ec2.
Right now, it will require you to define podTemplate for each "overloaded" replica, which will produce a lot of noise in chi.
Contributor guide
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 tracing how replica definitions and podTemplate settings are represented and applied in the operator. Define the expected replica-group configuration and verify that multiple replicas can share one template without repeated per-replica configuration. Done means the feature is implemented with coverage for regular and ephemeral replica groups.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100