Operator could not create Keeper Pods
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
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.
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)
- 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
-
[Regression / Discussion] Loss of hot-reloaded password rotation after removal of k8s_secret_* in 0.27.4Possibly taken @sunsingerus claimed this 1 day ago. Openplanned 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
-
[submenu] nil issue on ubuntu 26.04Possibly taken @egoist claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
prime-radiant-inc/evener#3873 ·
Maintainers usually reply within 1 day
-
extract_llm_sweep / cache_aware_summarizer prefix ask 400s when thinking.budget_tokens exceeds PrefixAskMaxTokensPossibly taken @amiddavid claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
rossoctl/context-guru#405 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
router-for-me/CLIProxyAPI#6423 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 2 days