Altinity / Altinity/helm-charts
manage CRDs with the helm chart
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 57
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
kube-prometheus-stack started doing something cool in v68 where they actually manage CRDs through the helm chart by having the chart spawn a pre-install job to upgrade the CRDs inside the cluster; see https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack/charts/crds for the implementation. It might be cool if this helm chart did something similar so we could stop having to manage CRD upgrades out-of-band...
Contributor guide
No contributing guide indexed for this repository
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 reading the referenced kube-prometheus-stack charts/crds implementation and compare it with this repository's ClickHouse Helm chart structure. Define the pre-install CRD upgrade behavior and verify that chart installation upgrades the CRDs in-cluster without requiring out-of-band management.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clickhouse, helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100