Altinity / Altinity/clickhouse-operator
Operator should not uninstall before managed resources
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
Problem: When the operator and CHI are included as part of the same helm release, uninstalling the helm release causes the CHI to be stuck in a hung state because the operator is uninstalled first.
I've researched it and chatted with other helm chart maintainers, and there is no reliable way to ensure a specific install / uninstall order across all of the ways that a helm chart can be used (e.g. through terraform or argo).
Suggested Fix: The Operator should prevent itself from being uninstalled until any pending CHI or CHK finalizers have resolved.
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
No file or test is named. Start by tracing the operator's uninstall and lifecycle handling, then inspect how pending CHI and CHK finalizers are observed. Done means the operator remains available until those finalizers resolve during Helm release removal, with lifecycle behavior covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100