Allow to set per-replica templates/settings
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- clickhouse, go, kubernetes
- Domain
- databases, devops, infrastructure
Research direction
No files, tests, or entry points are identified in the issue. Start by tracing how the operator represents replicas and applies templates/settings during reconciliation, then determine how per-replica configuration and external replicas should be represented in the API. Done means the proposed behavior supports version checks, per-shard customization, and the external-replica use case without requiring a full cluster rollout.
Written by the indexing model from the issue text.
Description
Use case
- Test version/config updates: allow us update/create single replica on the new version and verify compatibility manually before the full cluster rollout.
- Per-shard customization of disk size/weight/etc
- The same API can be used to specify external replicas to support #144
- Dominant language
- Go
- Stars
- 313
- Forks
- 48
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 21
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from ClickHouse/clickhouse-operator
-
feature
Difficulty 3/5 1-2 days Newbie friendliness 45/100
ClickHouse/clickhouse-operator#365 · 1 comment ·
Maintainers usually reply within 1 day
-
feature
Difficulty 5/5 Over a week Newbie friendliness 35/100
ClickHouse/clickhouse-operator#293 · 1 comment ·
Maintainers usually reply within 1 day
-
Write migration paths/helper tools to the operator from bitnami helmchart/Altinity operatorMay be free again @GrigoryPervakov claimed this 70 days ago, and no pull request is open. Openfeature
ClickHouse/clickhouse-operator#272 · 3 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
feat(controller): Allow for a configurable listen_host in network.yamlPossibly taken @arekborucki claimed this 120 days ago. Openfeature
Difficulty 4/5 3-5 days Newbie friendliness 48/100
ClickHouse/clickhouse-operator#217 · 1 comment ·
Maintainers usually reply within 1 day
-
feature
Difficulty 5/5 Over a week Newbie friendliness 35/100
ClickHouse/clickhouse-operator#144 · 2 reactions ·
Maintainers usually reply within 1 day
All issues in ClickHouse/clickhouse-operator
Similar issues
-
Routing rule or circuit breaker trip expression with an unknown CEL function hangs daprdPossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
[falco-talon] Setting `podAnnotations` makes the chart fail to renderPossibly taken @RaphaelFakhri claimed this today. Openneeds-kind
Difficulty 1/5 Under an hour Newbie friendliness 88/100
falcosecurity/charts#1084 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
DataDog/terraform-provider-datadog#4479 ·
Maintainers usually reply within 2 days
-
component/tests needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
NVIDIA/nodewright#967 ·
Maintainers usually reply within 1 day