Maintenance & Failover
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- kubernetes
- Domain
- databases, documentation, infrastructure
Research direction
Start with the three requested areas in the issue: Kubernetes maintenance and node removal, recovery when replacing a failed or corrupted node, and encryption for ClickHouse and ClickHouse Keeper. Identify the relevant official documentation and example manifests; done means the issue's questions are answered with authoritative references or concrete examples.
Written by the indexing model from the issue text.
Description
We're running a Kubernetes cluster with three worker nodes and are planning to deploy ClickHouse and ClickHouse Keeper version 25.8 using the Altinity ClickHouse Operator 0.25.3. However, I couldn’t find detailed documentation regarding maintenance tasks.
Specifically, I’d like to know:
- Is there any official guidance on temporarily or permanently removing a ClickHouse node from the cluster for maintenance purposes in Kubernetes?
- If a node fails or its disk becomes corrupted, will adding a new node with a new disk to the ClickHouse cluster automatically trigger replication to that node for data recovery?
- Are there any official documents or example manifests for enabling in-transit and at-rest encryption for both ClickHouse and ClickHouse Keeper to ensure secure communication?
Any references or best practices would be greatly appreciated.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 577
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 4
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the 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 Altinity/clickhouse-operator
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Altinity/clickhouse-operator#2093 ·
Maintainers usually reply within 2 days
-
planned for review
Difficulty 5/5 Over a week Newbie friendliness 38/100
Altinity/clickhouse-operator#2092 · 1 comment · 1 assignee ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Altinity/clickhouse-operator#2089 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
Altinity/clickhouse-operator#2064 · 3 comments ·
Maintainers usually reply within 2 days
-
big deployment planned for review
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Altinity/clickhouse-operator#2063 ·
Maintainers usually reply within 2 days
All issues in Altinity/clickhouse-operator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
slavakurilyak/awesome-ai-agents#710 ·
Maintainers usually reply within 1 day
-
`renderLinkedIssues` overshoots its byte budget: unresolved and omitted lists are never boundedOpenagent-butler-finding agent-research-recommend bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
jordansmall/spindrift#4614 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
weaviate/weaviate-go-client#485 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Auth server panics in GetProjectById when FindUsersByUID returns an errorPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
litmuschaos/litmus#5641 ·
Maintainers usually reply within 6 days