Altinity / Altinity/clickhouse-operator
Auto reconcile after update CHIT
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
Hi, we are trying to do user management in a separate repository using CHIT, but we ran into a problem, reconcile does not start when updating CHIT. It can be started manually using spec.taskID in CHE, but this is not suitable for our solution. Are there any workarounds to run reconline if something has changed, for example some resource: secret, cm or something else. CHI and CHIT are in different repositories
clickhouse-operator 0.23.5
clickhouse 24.3.9
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 by reproducing the behavior with clickhouse-operator 0.23.5 and ClickHouse 24.3.9, using CHI and CHIT in separate repositories. Trace the reconciliation entry point for CHIT updates and compare it with the manual spec.taskID trigger in CHE; done means an update to a resource such as a secret or ConfigMap starts reconciliation, or the supported workaround is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100