Altinity / Altinity/clickhouse-operator
Operator could not create Keeper Pods
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
Hi,
I have deployed altinity-clickhouse-operator:0.25.6 and deployed altinity clickhouse helm-chart with enabled clickhouse installation(CHI) and keeper(CHK) to manage repliacation between clickhouse pods. Operator and CR deployments are in same k8s cluster but in different namespaces. Operator deploys ClickhouseInstallation successfully. However it does not deploy Keeper pods.I have checked operator logs, events, and states of resources. There is no significant information or issue to point out issue. Keeper states InProgress. It seems Operator couldnot or does not try to deploy. Do you know whether there is some configuration is missing or is this an operator/helmchart bug.
All details are in this issue link(I have already created an issue on helm chart repo - > https://github.com/Altinity/helm-charts/issues/117)
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 with the linked Helm chart issue and the operator logs, events, and CHI/CHK resource states described here; compare the operator and custom resource namespaces and the Keeper configuration. Done means the operator creates the Keeper pods and the Keeper resource leaves InProgress with replication managed successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100