Altinity / Altinity/clickhouse-operator
Modify status for clickhouseinstallation to support kstatus
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 574
- Avg merge
- 8d 6h
- Merged PRs (30d)
- 6
Description
Doc: https://github.com/kubernetes-sigs/cli-utils/tree/master/pkg/kstatus
This would allow helathchecking during deployment using gitops tools. For example FluxCD relies on kstatus for healthchecking CRDs - https://fluxcd.io/flux/components/kustomize/kustomization/#health-assessment
Also helm is discussing the usage of kstatus in the future.
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 cli-utils kstatus documentation linked in the issue and the ClickHouseInstallation resource in this repository. Determine which status information FluxCD and other kstatus consumers require, then verify the result against the linked Flux health-assessment documentation. Done means ClickHouseInstallation health is recognized during deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100