jetstack / jetstack/version-checker
Publish helm chart also as an OCI package (e.g. on GHCR/quay.io registry)
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 778
- Forks
- 82
- Avg merge
- 2m
- Merged PRs (30d)
- 3
Description
The helm chart of version-checker is published using the classic approach with a static webserver and an index.yaml.
In helm 3.8+ the OCI method went GA:
- https://blog.bitnami.com/2023/04/httpsblog.bitnami.com202304bitnami-helm-charts-now-oci.html?m=1
- https://helm.sh/docs/topics/registries/
- https://github.com/helm/helm/releases/tag/v3.8.0
I see two options to use as an OCI mirror:
- GHCR (Github packages)
You need to think about the Github organizational plan. On free plan there are 500MB included - Quay.io (where you also push the container images)
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 locating the version-checker Helm chart and the workflow that publishes it with the current static webserver and index.yaml approach. Read the linked Helm 3.8+ registry documentation, then determine whether GHCR or Quay.io is suitable; done means the chart is also published as an installable OCI package.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, helm
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100