You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GHCR (Github packages)
You need to think about the Github organizational plan. (Free plan only includes 500MB)
AWS ECR (where you mostly push your container images)
If you would fully rely on native Github actions to produce these artifacts, the change would be super simple
- name: Run chart-releaseruses: helm/[email protected]env:
CR_TOKEN: "${{ secrets.GITHUB_TOKEN }}"CR_GENERATE_RELEASE_NOTES: true# ================# below this line is relevant for OCI publishing# ================
- name: Login to GitHub Container Registryuses: docker/login-action@v3with:
registry: ghcr.iousername: ${{ github.actor }}password: ${{ secrets.GITHUB_TOKEN }}
- name: Push charts to GHCRrun: | shopt -s nullglob for pkg in .cr-release-packages/*; do if [ -z "${pkg:-}" ]; then break fi helm push "${pkg}" "oci://ghcr.io/${GITHUB_REPOSITORY_OWNER}/charts" done
Is your feature request related to a problem?
No
Is your feature request related to a specific Helm chart, if yes mention name of the chart?
All helm charts
Describe the solution you'd like
The helm charts are published using the classic approach with a static webserver and an index.yaml (GitHub pages):
However in helm 3.8+ the OCI method went GA:
I see two options to use as an OCI mirror:
You need to think about the Github organizational plan. (Free plan only includes 500MB)
If you would fully rely on native Github actions to produce these artifacts, the change would be super simple
Source: https://github.com/prometheus-community/helm-charts/blob/4bbd07f308884d44d0edff23ee60da967dc2cd23/.github/workflows/release.yaml#L39C1-L61C15
Also a lot of other CNCF projects are using this approach.
Describe alternatives you've considered
Still using the old approach with the index.yaml and static website.
The text was updated successfully, but these errors were encountered: