Altinity / Altinity/helm-charts
Do not update keeper replica count
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 57
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
reading the helm chart values there is this comment # !! DO NOT CHANGE AFTER INITIAL DEPLOYMENT:
https://github.com/Altinity/helm-charts/blame/13b84720f0f6c728d270e737b7f9a14fc476c6d5/charts/clickhouse/values.yaml#L203
but following the git blame + pull-request does not provide sufficient context for:
- Why we should not change the ch-keeper replication count and context behind this comment
- How we can actually change the replication count after deployment
Could this be updated to provide sufficient context i.e by linking to the altinity knowledge base or other documentation?
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 charts/clickhouse/values.yaml around line 203, then follow the linked git blame and pull request for the existing keeper replica-count comment. Confirm the reason the count should not change after deployment and how it can be changed, using the Altinity knowledge base or other documentation mentioned in the issue. Done means the comment links to sufficient context and instructions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, yaml
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100