Altinity / Altinity/clickhouse-operator
feature request: support autoscaling ClickHouse cluster
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
It would be really useful to support autoscaling clickhouse cluster based on some events or metrics similar to how KEDA does.
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 examining the clickhouse-operator's existing cluster-management entry points and how it exposes or consumes events and metrics. Define the autoscaling behavior and its KEDA-like trigger model before making changes; done means the operator can autoscale a ClickHouse cluster from specified events or metrics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100